You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/10/08 11:42:00 UTC
[jira] [Commented] (SOLR-13376) Multi-node race condition to
create/remove nodeLost markers
[ https://issues.apache.org/jira/browse/SOLR-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946755#comment-16946755 ]
ASF subversion and git services commented on SOLR-13376:
--------------------------------------------------------
Commit 8c144444fe3f71e5a5131432b1285ebff518ccb0 in lucene-solr's branch refs/heads/master from Andrzej Bialecki
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=8c14444 ]
SOLR-13376: Multi-node race condition to create/remove nodeLost markers.
> Multi-node race condition to create/remove nodeLost markers
> -----------------------------------------------------------
>
> Key: SOLR-13376
> URL: https://issues.apache.org/jira/browse/SOLR-13376
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: 8.3
>
> Attachments: SOLR-13376.patch
>
>
> NodeMarkersRegistrationTest.testNodeMarkersRegistration is frequently failing on jenkins builds in the same spot, with a similar looking logs.
> Although i haven't been able to reproduce these failures locally, I am fairly confident that the problem is a race condition bug that exists between when/how a new Overseer will process & clean up "nodeLost" marker's in ZK, with how other nodes may (mistakenly) re-create those markers in their liveNodes listener.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org