You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by sh...@apache.org on 2018/08/02 02:38:55 UTC
lucene-solr:jira/solr-12607: SOLR-12607: Added entry to CHANGES.txt
Repository: lucene-solr
Updated Branches:
refs/heads/jira/solr-12607 c55ce4d0f -> d581fa36f
SOLR-12607: Added entry to CHANGES.txt
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/d581fa36
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/d581fa36
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/d581fa36
Branch: refs/heads/jira/solr-12607
Commit: d581fa36f83e0f088d1a15b9a283b6d38e6cb74e
Parents: c55ce4d
Author: Shalin Shekhar Mangar <sh...@apache.org>
Authored: Thu Aug 2 08:08:48 2018 +0530
Committer: Shalin Shekhar Mangar <sh...@apache.org>
Committed: Thu Aug 2 08:08:48 2018 +0530
----------------------------------------------------------------------
solr/CHANGES.txt | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/d581fa36/solr/CHANGES.txt
----------------------------------------------------------------------
diff --git a/solr/CHANGES.txt b/solr/CHANGES.txt
index 2d8db8c..e35e22c 100644
--- a/solr/CHANGES.txt
+++ b/solr/CHANGES.txt
@@ -184,7 +184,13 @@ Bug Fixes
* SOLR-12477: An update would return a client error(400) if it hit a AlreadyClosedException.
We now return the error as a server error(500) instead (Jeffery via Varun Thacker)
-* SOLR-12606: Fix InfixSuggestersTest.testShutdownDuringBuild() failures. (Steve Rowe)
+* SOLR-12606: Fix InfixSuggestersTest.testShutdownDuringBuild() failures. (Steve Rowe)
+
+* 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. (Cao Manh Dat, shalin)
Optimizations
----------------------