You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2018/03/14 21:32:00 UTC

[jira] [Commented] (ACCUMULO-4828) Initialization of master deadlocks

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

Christopher Tubbs commented on ACCUMULO-4828:
---------------------------------------------

Sadly, it does not look like the IT timeouts I was seeing were related to this (they were instead related to ACCUMULO-4847). Hopefully the VFS2.2 update fixes it.

> Initialization of master deadlocks
> ----------------------------------
>
>                 Key: ACCUMULO-4828
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4828
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: stuck-master-jstack.txt
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> See the attached jstack. It appears that thread trying to watch ZK for the location of the monitor is blocking the instantiation of the Master because of some VFS call which is never completing.
> I think we have two threads taking overlapping locks.



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