[
https://issues.apache.org/jira/browse/SOLR-16416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624156#comment-17624156
]
ASF subversion and git services commented on SOLR-16416:
--------------------------------------------------------
Commit e636590600206c8cae9f88fabab5f962fe984937 in solr's branch
refs/heads/branch_9_1 from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=e6365906002 ]
SOLR-16416: retry overseerPrioritizer ops on failure. (#1129)
(cherry picked from commit 1738098b348a27b3dd5c4f64e12115de20b74b17)
> Fix silently failing Overseer Election joinAtHead during
> testDesignatedOverseerRestarts
> ---------------------------------------------------------------------------------------
>
> Key: SOLR-16416
> URL: https://issues.apache.org/jira/browse/SOLR-16416
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Houston Putman
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> OverseerRolesTest.testDesignatedOverseerRestarts has been failing
> consistently (around 2.5% of the time). I think this is because
> LeaderElection.joinElection does not respect the joinAtHead flag, if
> connectionIssues happen while setting the leader election nodes.
> LeaderElection does not use the automatic retryOnConnLoss flags when doing zk
> operations. Instead, it waits for an error to come back, and it handles the
> retry itself. This is fine for the normal case, because it checks if node is
> represented in the leaderElection child nodes, and if so it ignores the
> connection loss. However when doing joinAtHead, if the childNode exists, but
> isn't at the place it should be, then the manual retry should be exercised.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
