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

ASF subversion and git services commented on SOLR-12626:
--------------------------------------------------------

Commit d82fc7c3b5f038f11fac6e00a8eba828d17a4cf1 in lucene-solr's branch 
refs/heads/branch_7x from Tomas Fernandez Lobbe
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d82fc7c ]

SOLR-12626: TestInjection.waitForInSyncWithLeader retries in case of errors

When waiting for follower replicas to be in sync with the leader, 
TestInjection.waitForInSyncWithLeader
now keeps waiting even if it gets an exception while trying to get leader's 
replication details. The
method will only exit when it exhausts the number of retries or succeeds.


> TestInjection.waitForInSyncWithLeader should keep retrying after connection 
> issues
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-12626
>                 URL: https://issues.apache.org/jira/browse/SOLR-12626
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Tests
>            Reporter: Tomás Fernández Löbbe
>            Assignee: Tomás Fernández Löbbe
>            Priority: Minor
>             Fix For: master (8.0), 7.5
>
>         Attachments: SOLR-12626.patch
>
>
> {{waitForInSyncWithLeader}} currently returns "false" making asserts fail 
> when an exception is thrown while checking if the core is in sync with the 
> leader. This can cause things like the leader being down (i.e. in ChaosMonkey 
> tests) to fail asserts in followers. Instead, we should continue iterating 
> the remaining amount of times.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to