I did some testing of several search words with 1 node, 1 index with 5
shards and no replicas.
Later I set 1 replica for the index, activated a new node with same cluster
name on another machine, the node identified the master and created the
replicas.
I ran the same text search as before, this time 2 nodes running, and I got
a smaller amount of hits for the same search text.
I also tried running only node 1, and also only node 2, but I still get the
same missing results.
Later I set 1 replica for the index, activated a new node with same
cluster name on another machine, the node identified the master and
created the replicas.
I ran the same text search as before, this time 2 nodes running,
and I got a smaller amount of hits for the same search text.
Double check that the primaries still have the number you thought
they did. It could be that something changed in your index and you
perhaps forgot? Even better, check that the primaries and replicas
have the same number of docs. An easy way to check is with es shards -v using the GitHub - elastic/es2unix: Command-line ES
utility. The doc counts for each shard's p' and r' should match.
When I shut down node 2 that has the replicas and work only with node 1
with the primaries,
I still get smaller amount of hits than before I activated the replica for
the index.
Doesn't it mean that the problem is not about different number of docs in
primaries and replicas?
Thanks, Ophir
On Monday, February 18, 2013 7:16:47 PM UTC+2, Ophir Michaeli wrote:
Hi,
I did some testing of several search words with 1 node, 1 index with 5
shards and no replicas.
Later I set 1 replica for the index, activated a new node with same
cluster name on another machine, the node identified the master and created
the replicas.
I ran the same text search as before, this time 2 nodes running, and I got
a smaller amount of hits for the same search text.
I also tried running only node 1, and also only node 2, but I still get
the same missing results.
When I shut down node 2 that has the replicas and work only with node 1
with the primaries,
I still get smaller amount of hits than before I activated the replica for
the index.
Doesn't it mean that the problem is not about different number of docs in
primaries and replicas?
Thanks, Ophir
On Monday, February 18, 2013 8:38:56 PM UTC+2, Drew Raines wrote:
Ophir Michaeli wrote:
Later I set 1 replica for the index, activated a new node with same
cluster name on another machine, the node identified the master and
created the replicas.
I ran the same text search as before, this time 2 nodes running,
and I got a smaller amount of hits for the same search text.
Double check that the primaries still have the number you thought
they did. It could be that something changed in your index and you
perhaps forgot? Even better, check that the primaries and replicas
have the same number of docs. An easy way to check is with es shards -v using the GitHub - elastic/es2unix: Command-line ES
utility. The doc counts for each shard's p' and r' should match.
can you maybe give some more information about what is going on?
are you doing a search and the number of returned hits is less than before
or do you look at the number of documents in the index?
simon
On Tuesday, February 19, 2013 10:36:08 AM UTC+1, Ophir Michaeli wrote:
When I shut down node 2 that has the replicas and work only with node 1
with the primaries,
I still get smaller amount of hits than before I activated the replica for
the index.
Doesn't it mean that the problem is not about different number of docs in
primaries and replicas?
Thanks, Ophir
On Monday, February 18, 2013 8:38:56 PM UTC+2, Drew Raines wrote:
Ophir Michaeli wrote:
Later I set 1 replica for the index, activated a new node with same
cluster name on another machine, the node identified the master and
created the replicas.
I ran the same text search as before, this time 2 nodes running,
and I got a smaller amount of hits for the same search text.
Double check that the primaries still have the number you thought
they did. It could be that something changed in your index and you
perhaps forgot? Even better, check that the primaries and replicas
have the same number of docs. An easy way to check is with es shards -v using the GitHub - elastic/es2unix: Command-line ES
utility. The doc counts for each shard's p' and r' should match.
Yes, I'm doing search and the number of returned hits is less than before
setting 1 replica and opening another node.
On Tuesday, February 19, 2013 12:03:56 PM UTC+2, simonw wrote:
Hey Ophir,
can you maybe give some more information about what is going on?
are you doing a search and the number of returned hits is less than before
or do you look at the number of documents in the index?
simon
On Tuesday, February 19, 2013 10:36:08 AM UTC+1, Ophir Michaeli wrote:
When I shut down node 2 that has the replicas and work only with node 1
with the primaries,
I still get smaller amount of hits than before I activated the replica
for the index.
Doesn't it mean that the problem is not about different number of docs in
primaries and replicas?
Thanks, Ophir
On Monday, February 18, 2013 8:38:56 PM UTC+2, Drew Raines wrote:
Ophir Michaeli wrote:
Later I set 1 replica for the index, activated a new node with same
cluster name on another machine, the node identified the master and
created the replicas.
I ran the same text search as before, this time 2 nodes running,
and I got a smaller amount of hits for the same search text.
Double check that the primaries still have the number you thought
they did. It could be that something changed in your index and you
perhaps forgot? Even better, check that the primaries and replicas
have the same number of docs. An easy way to check is with es shards -v using the GitHub - elastic/es2unix: Command-line ES
utility. The doc counts for each shard's p' and r' should match.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.