Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 26 Apr 2012 11:39:18 +0000 (UTC)
From: "Jens Bo Rasmussen (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1326439927.4853.1335440359001.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1719865953.4843.1335440237868.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (SOLR-3417) Data is not replicated when empty
 replica slices become leader slices
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SOLR-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Bo Rasmussen updated SOLR-3417:
------------------------------------

    Description: 
Scenario: ensure that data is replicated when empty replica slices become leader slices
Given a SolrCloud cluster is running with
number of servers (Solr nodes): 2
number of slices per node: 1
number of replica per slice: 0
number of documents in leader slice on first Solr node: 4
number of documents in leader slice on second Solr node: 1
When I configure each node with 1 replica per slice
And I stop all nodes
And I start the nodes one at a time
Then I would expect that the SolrCloud cluster is running with
number of servers (Solr nodes): 2
number of slices per node: 1
number of replica per slice: 1
number of documents in leader slice on first Solr node: 4
number of documents in replica slice on second Solr node: 4
number of documents in leader slice on first Solr node: 1
number of documents in replica slice on second Solr node: 1

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 leader slice on first Solr node: 4
number of documents in replica slice on second Solr node: 0
number of documents in leader slice on first Solr node: 0
number of documents in replica slice on second Solr node: 1

When the first Solr node is started the added replica slices are declared leaders (with 0 documents obviously)
When the second Solr node is started the slices which were previously leaders are declared replica
And the data is not replicated from the leader slices to the replica slices or vice versa
==> data is not replicated

  was:
Scenario: ensure that data is replicated when empty replica slices become leader slices
Given a SolrCloud cluster is running with
number of servers (Solr nodes): 2
number of slices per node: 1
number of replica per slice: 0
number of documents in leader slice on first Solr node: 4
number of documents in leader slice on second Solr node: 1

When I configure each node with 1 replica per slice
And I stop all nodes
And I start the nodes one at a time
Then I would expect that the SolrCloud cluster is running with
number of servers (Solr nodes): 2
number of slices per node: 1
number of replica per slice: 1
number of documents in leader slice on first Solr node: 4
number of documents in replica slice on second Solr node: 4
number of documents in leader slice on first Solr node: 1
number of documents in replica slice on second Solr node: 1

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 leader slice on first Solr node: 4
number of documents in replica slice on second Solr node: 0
number of documents in leader slice on first Solr node: 0
number of documents in replica slice on second Solr node: 1

When the first Solr node is started the added replica slices are declared leaders (with 0 documents obviously)
When the second Solr node is started the slices which were previously leaders are declared replica
And the data is not replicated from the leader slices to the replica slices or vice versa
==> data is not replicated

    
> Data is not replicated when empty replica slices become leader slices
> ---------------------------------------------------------------------
>
>                 Key: SOLR-3417
>                 URL: https://issues.apache.org/jira/browse/SOLR-3417
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 4.0
>         Environment: 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 0 replica
>            Reporter: Jens Bo Rasmussen
>            Priority: Minor
>              Labels: replica
>             Fix For: 4.1
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Scenario: ensure that data is replicated when empty replica slices become leader slices
> Given a SolrCloud cluster is running with
> number of servers (Solr nodes): 2
> number of slices per node: 1
> number of replica per slice: 0
> number of documents in leader slice on first Solr node: 4
> number of documents in leader slice on second Solr node: 1
> When I configure each node with 1 replica per slice
> And I stop all nodes
> And I start the nodes one at a time
> Then I would expect that the SolrCloud cluster is running with
> number of servers (Solr nodes): 2
> number of slices per node: 1
> number of replica per slice: 1
> number of documents in leader slice on first Solr node: 4
> number of documents in replica slice on second Solr node: 4
> number of documents in leader slice on first Solr node: 1
> number of documents in replica slice on second Solr node: 1
> 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 leader slice on first Solr node: 4
> number of documents in replica slice on second Solr node: 0
> number of documents in leader slice on first Solr node: 0
> number of documents in replica slice on second Solr node: 1
> When the first Solr node is started the added replica slices are declared leaders (with 0 documents obviously)
> When the second Solr node is started the slices which were previously leaders are declared replica
> And the data is not replicated from the leader slices to the replica slices or vice versa
> ==> data is not replicated

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org