Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 17 Oct 2016 13:12:58 +0000 (UTC)
From: "Alexandre Rafalovitch (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12553129.1335529693000.3999.1476709978414@Atlassian.JIRA>
In-Reply-To: <JIRA.12553129.1335529693000@Atlassian.JIRA>
References: <JIRA.12553129.1335529693000@Atlassian.JIRA> <JIRA.12553129.1335529693980@arcas>
Subject: [jira] [Commented] (SOLR-3420) Data is not replicated from replica
 slices to leader slices
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 17 Oct 2016 13:13:00 -0000


    [ https://issues.apache.org/jira/browse/SOLR-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582218#comment-15582218 ] 

Alexandre Rafalovitch commented on SOLR-3420:
---------------------------------------------

Ancient bug report that was never reviewed or confirmed. A bit late to worry about this one now?

> Data is not replicated from replica slices to leader slices
> -----------------------------------------------------------
>
>                 Key: SOLR-3420
>                 URL: https://issues.apache.org/jira/browse/SOLR-3420
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 4.0-ALPHA
>         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 1 replica
>            Reporter: Jens Bo Rasmussen
>              Labels: replica
>             Fix For: 4.9, 6.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> 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


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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