You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elasticsearch version:
2.2 JVM version:
1.8 OS version:
debian 8.4 Description of the problem including expected versus actual behavior:
Cluster with 3 nodes . Data is being pushed to node 1 in the cluster in bulk => total count 1 million .
After bulk operation complete shutting down node 1 .
Running query to count docs the number is the same as before node 1 shutdown 1 million.
deleting the index .
Counting the number of docs once again => no data
starting node 1 => there are docs but less then 1 million (~800k) .
The expected results is to have none . The join node should get sync with the current master .
Steps to reproduce:
3 nodes cluster pushing data in bulk using the current master node IP
stop the master node
3.delete the index
start the previous master node
The index have data again but not as its original count
Provide logs (if relevant):
Describe the feature:
The text was updated successfully, but these errors were encountered:
@aloneldi the fix is 5.0 only sadly - the fix is quite tricky and will not be ported to 2.x.
PS. you can see that reflected by the labels in the #18249 . Also check the corresponding PR, #18250 for some extra background and discussion (if you want)
Elasticsearch version:
2.2
JVM version:
1.8
OS version:
debian 8.4
Description of the problem including expected versus actual behavior:
Cluster with 3 nodes . Data is being pushed to node 1 in the cluster in bulk => total count 1 million .
After bulk operation complete shutting down node 1 .
Running query to count docs the number is the same as before node 1 shutdown 1 million.
deleting the index .
Counting the number of docs once again => no data
starting node 1 => there are docs but less then 1 million (~800k) .
The expected results is to have none . The join node should get sync with the current master .
Steps to reproduce:
3.delete the index
Provide logs (if relevant):
Describe the feature:
The text was updated successfully, but these errors were encountered: