Details
-
Bug
-
Resolution: Won't Fix
-
Test Blocker
-
4.0.0
-
Security Level: Public
-
4 Data nodes: 172.23.100.17-20, 1 Query node 172.23.100.21, 1 index node 172.23.100.22.
cbq-engine started on node .21 as /opt/couchbase/bin/cbq-engine --datastore=http://127.0.0.1:8091 --http=:8093 --configstore=http://127.0.0.1:8091
-
Untriaged
-
Centos 64-bit
-
Unknown
Description
cpq run on client machine 172.23.100.28.
cbq -engine=http://172.23.100.21:8093
cbq> select * from system:indexes;
{
"requestID": "9e7aa7bf-70d4-4faa-ac19-dada5c63b7ec",
"signature":
,
"results": [
],
"errors": [
{
"code": 11000,
"msg": "System datastore error - cause: Failed to load indexes for keyspace bucket-1 - cause: HTTP error 400 Bad Request getting \"http://127.0.0.1:8091/pools/default/buckets/bucket-1/ddocs\":
"
}
],
"status": "errors",
"metrics":
}
you will see that it reports a system error failiing to access meta data on 127.0.0.1:8091. the metadata is on 172.23.100.17-20.
if i stop this automatically started cpq-engine (created by adding a node with service Query only thru console)
and restart it with cbq-engine -datastore=http://172.23.100.17, the above issue retrieving system:indexes went away.
Attachments
Issue Links
- relates to
-
MB-13624 While 'CREATE PRIMARY INDEX' is executing, 'SELECT * from system:indexes" fails with Panic: runtime error"
- Closed