[ https://issues.apache.org/jira/browse/ACCUMULO-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916090#comment-13916090 ]
ASF subversion and git services commented on ACCUMULO-2422: ----------------------------------------------------------- Commit 7d70ef5848cf6b42752ec708e0442d4b7aa98c2f in accumulo's branch refs/heads/1.6.0-SNAPSHOT from [~ecn] [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=7d70ef5 ] ACCUMULO-2422 reset watch on non-delete events > Backup master can miss acquiring lock when primary exits > -------------------------------------------------------- > > Key: ACCUMULO-2422 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2422 > Project: Accumulo > Issue Type: Bug > Components: fate, master > Affects Versions: 1.5.1 > Reporter: Bill Havanki > Assignee: Bill Havanki > Priority: Critical > Labels: failover, locking > Fix For: 1.6.0, 1.5.2 > > > While running randomwalk tests with agitation for the 1.5.1 release, I've > seen situations where a backup master that is eligible to grab the master > lock continues to wait. When this condition arises and the other master > restarts, both wait for the lock without success. > I cannot reproduce the problem reliably, and I think more investigation is > needed to see what circumstances could be causing the problem. -- This message was sent by Atlassian JIRA (v6.1.5#6160)