Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
4.0-ALPHA
-
None
-
Linux 2.6.32-29-server #58-Ubuntu SMP Fri Feb 11 21:06:51 UTC 2011 x86_64 GNU/Linux, Solr snapshot from 29th of February 2012, 2 Solr machines with 1 slice each and 1 replica
Description
Scenario: ensure that data is not lost when leader slices and replica slices switch roles due to an untimely restart of both nodes
Given a SolrCloud cluster is running with
number of nodes: 2
number of slices per node: 1
number of documents in leader slice1_shard1 on first Solr node: 1
number of documents in replica slice2_shard1 on second Solr node: 1
number of documents in leader slice2_shard2 on first Solr node: 1
number of documents in replica slice1_shard2 on second Solr node: 1
And the second node is stopped
And x new documents are added to each slice on the first node
And the first node is stopped
When the second node is started and the slices become leader slices
And the first node is started and the slices become replica slices
Then I would expect that the SolrCloud cluster is running with
number of nodes: 2
number of slices per node: 1
number of documents in replica slice1_shard1 on first Solr node: 1+x
number of documents in leader slice2_shard1 on second Solr node: 1+x
number of documents in replica slice2_shard2 on first Solr node: 1+x
number of documents in leader slice1_shard2 on second Solr node: 1+x
Testresult: data is not replicated
number of servers (Solr nodes): 2
number of slices per node: 1
number of replica per slice: 1
number of documents in replica slice1_shard1 on first Solr node: 1+x
number of documents in leader slice2_shard1 on second Solr node: 1
number of documents in replica slice2_shard2 on first Solr node: 1+x
number of documents in leader slice1_shard2 on second Solr node: 1
==> data is not replicated from replica slices to leader slices
