Indexing is stopped and I see the same results after a refresh - the
replica is off by 362 docs.
The shard that is off - shard 0 - is on the master node. In those logs I
see some recovery/rebalancing statements:
[2011-10-18 19:42:53,551][DEBUG][gateway.local ] [es_db3]
[users_production][0]: allocating [[users_production][0], node[null],
[P], s[UNASSIGNED]] to
[[es_db3][3OIKkft6QeSGsjRE9TuIKg][inet[/:9300]]] on primary allocation
[2011-10-18 19:43:31,655][DEBUG][action.admin.indices.status] [es_db3]
[users_production][0], node[3OIKkft6QeSGsjRE9TuIKg], [P],
s[INITIALIZING]: Failed to execute
[org.elasticsearch.action.admin.indices.status.IndicesStatusRequest@5cb27de5]
org.elasticsearch.index.IndexShardMissingException:
[users_production][0] missing
at
org.elasticsearch.index.service.InternalIndexService.shardSafe(InternalIndexService.java:174)
at
org.elasticsearch.action.admin.indices.status.TransportIndicesStatusAction.shardOperation(TransportIndicesStatusAction.java:135)
at
org.elasticsearch.action.admin.indices.status.TransportIndicesStatusAction.shardOperation(TransportIndicesStatusAction.java:58)
at
org.elasticsearch.action.support.broadcast.TransportBroadcastOperationAction$AsyncBroadcastAction.performOperation(TransportBroadcastOperationAction.java:231)
at
org.elasticsearch.action.support.broadcast.TransportBroadcastOperationAction$AsyncBroadcastAction.performOperation(TransportBroadcastOperationAction.java:209)
at
org.elasticsearch.action.support.broadcast.TransportBroadcastOperationAction$AsyncBroadcastAction$1.run(TransportBroadcastOperationAction.java:185)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
[2011-10-18 19:44:02,225][DEBUG][index.gateway ] [es_db3]
[users_production][0] starting recovery from local ...
[2011-10-18 19:44:05,655][DEBUG][index.gateway ] [es_db3]
[users_production][0] recovery completed from local, took [3.4s]
index : files [241] with total_size [2.3gb], took[31ms]
: recovered_files [0] with total_size [0b]
: reusing_files [241] with total_size [2.3gb]
translog : number_of_operations [0], took [3.4s]
[2011-10-18 19:45:37,834][DEBUG][gateway.local ] [es_db3]
[users_production][0]: allocating [[users_production][0], node[
null], [R], s[UNASSIGNED]] to
[[es_db0][4P-nUocJRTCrYQ5bH3TRUQ][inet[/:9300]]] in order to reuse
its unallocated persistent store with total_size [2.3gb]
I'm seeing these for all the shards though. I also see similar things on
the server with the replica. Is there something I should look for?
Thanks for the help!
Dave
Shay Banon wrote:
Also, any failures in the log?
On Sun, Oct 23, 2011 at 2:17 AM, Shay Banon <kimchy@gmail.com
mailto:kimchy@gmail.com> wrote:
Are indexing going on when you execute the test? Can you try and
refresh and see if you still get it?
On Sat, Oct 22, 2011 at 8:46 PM, sakrafd <dave@signalhq.com
<mailto:dave@signalhq.com>> wrote:
I'm seeing the same thing:
curl -X GET
"http://localhost:9200/users_production/user/_count?q=user_access_id:742"
{"count":23517808,"_shards":{"total":10,"successful":10,"failed":0}}
curl -X GET
"http://localhost:9200/users_production/user/_count?q=user_access_id:742"
{"count":23518180,"_shards":{"total":10,"successful":10,"failed":0}}
curl -X GET
"http://localhost:9200/users_production/user/_count?q=user_access_id:742"
{"count":23517808,"_shards":{"total":10,"successful":10,"failed":0}}
curl -X GET
"http://localhost:9200/users_production/user/_count?q=user_access_id:742"
{"count":23518180,"_shards":{"total":10,"successful":10,"failed":0}}
When I look at doc counts for each shard/replica (through
elastic-search-head), i can see that one shard and replica is off:
Primary:
docs: {
num_docs: 3082198
max_doc: 3545713
deleted_docs: 463515
}
Replica:
docs: {
num_docs: 3081671
max_doc: 3520572
deleted_docs: 438901
}
Is there a way to synch these without re-indexing?
Also, just curious - what's the difference between num_docs
and max_docs?
Thanks,
Dave
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Question-Inconsistent-count-results-tp873957p3444017.html
Sent from the ElasticSearch Users mailing list archive at
Nabble.com.