[
https://issues.apache.org/jira/browse/SOLR-12412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16560568#comment-16560568
]
Cao Manh Dat commented on SOLR-12412:
-------------------------------------
Hi [~varunthacker] ,
1st question: this is the only way to avoid the cache of the directory and
trigger merge reliable -> tragic event will reliably occur. You can try to
change the code to your strategy and valid that tragic event, in that case,
won't occur reliably.
2nd: Yeah, I plan to do that, but too busy with other stuff and it only makes
the test less clear. not affect the case I want to test. That comment mean, we
won't be able to recover shard to come active, since the leader is already
corrupted hence the replica won't be able to do recovery.
> Leader should give up leadership when IndexWriter.tragedy occur
> ---------------------------------------------------------------
>
> Key: SOLR-12412
> URL: https://issues.apache.org/jira/browse/SOLR-12412
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
> Fix For: master (8.0), 7.5
>
> Attachments: SOLR-12412.patch, SOLR-12412.patch,
> jenkins-failure-2325.log
>
>
> When a leader meets some kind of unrecoverable exception (ie:
> CorruptedIndexException). The shard will go into the readable state and human
> has to intervene.
> In that case, if there are another active replica in the same shard, the
> leader should give up its leadership.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
