[
https://issues.apache.org/jira/browse/SOLR-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566281#comment-16566281
]
ASF subversion and git services commented on SOLR-12607:
--------------------------------------------------------
Commit 259bc2baf7ce58aa0143fa6a8d43da417506cd63 in lucene-solr's branch
refs/heads/master from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=259bc2b ]
SOLR-12607: Fixed two separate bugs in shard splits which can cause data loss.
The first case is when using TLOG replicas only, the updates forwarded from
parent shard leader to the sub-shard leader are written only in tlog and not
the index. If this happens after the buffered updates have been replayed then
the updates can never be executed even though they remain the transaction log.
The second case is when synchronously forwarding updates to sub-shard leader
fails and the underlying errors are not propagated to the client
> Investigate ShardSplitTest failures
> -----------------------------------
>
> Key: SOLR-12607
> URL: https://issues.apache.org/jira/browse/SOLR-12607
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Fix For: master (8.0), 7.5
>
>
> There have been many recent ShardSplitTest failures.
> According to http://fucit.org/solr-jenkins-reports/failure-report.html
> {code}
> Class: org.apache.solr.cloud.api.collections.ShardSplitTest
> Method: testSplitWithChaosMonkey
> Failures: 72.32% (81 / 112)
> Class: org.apache.solr.cloud.api.collections.ShardSplitTest
> Method: test
> Failures: 26.79% (30 / 112)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
