Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
4.5.0
-
Untriaged
-
Unknown
Description
130 Data nodes, 1 index, 1 Query
Bucket has 60M items.
I tried to create a primary index on the bucket, and was unable.
create primary index on `default0`;
|
{
|
"requestID": "7e1a4e64-93fb-4ee7-847f-b73b52ce765a",
|
"signature": null,
|
"results": [
|
],
|
"errors": [
|
{
|
"code": 5000,
|
"msg": "GSI CreatePrimaryIndex() - cause: Fails to create index. There is no available index service that can process this request at this time. Index Service can be in bootstrap, recovery, or non-reachable. Please retry the operation at a later time."
|
}
|
],
|
"status": "errors",
|
"metrics": {
|
"elapsedTime": "10.004544498s",
|
"executionTime": "10.004496363s",
|
"resultCount": 0,
|
"resultSize": 0,
|
"errorCount": 1
|
}
|
}
|
Saw these errors in index log
2016-05-20T01:26:18.649+00:00 [Error] KVSender::sendShutdownTopic Unexpected Error During Shutdown Projector ec2-54-174-100-204.compute-1.amazonaws.com:9999 Topic MAINT_STREAM_TOPIC_3:f9:a3:f0:33:d9:5a:8c. Err Post http://ec2-54-174-100-204.compute-1.amazonaws.com:9999/adminport/shutdownTopicRequest: dial tcp 10.0.24.249:9999: i/o timeout
|
|
|
2016-05-20T01:26:18.649+00:00 [Error] KVSender::closeMutationStream MAINT_STREAM Error Received Post http://ec2-54-174-100-204.compute-1.amazonaws.com:9999/adminport/shutdownTopicRequest: dial tcp 10.0.24.249:9999: i/o timeout from ec2-54-174-100-204.compute-1.amazonaws.com:9999
|
|
|
2016-05-20T01:26:18.649+00:00 [Info] KVSender::sendShutdownTopic Projector ec2-54-174-109-179.compute-1.amazonaws.com:9999 Topic MAINT_STREAM_TOPIC_3:f9:a3:f0:33:d9:5a:8c
|
I later reconfigured the server for 92 Data nodes, 20 Index, 20 Query and the result was same. Could not create indexer on cluster. And UI reports that indexer services aren't available (screen)
