[
https://issues.apache.org/jira/browse/HBASE-22386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837383#comment-16837383
]
Sean Mackrory commented on HBASE-22386:
---------------------------------------
Huh - with the default configuration all tests are passing for me. By any
chance, are you setting fs.hboss.sync.zk.connectionString to a path that
doesn't already exist in auth-keys.xml? I'd be a little surprised if you were,
but that's the only thing I can think of that was cause this if we're on
otherwise identical code.
> HBOSS: Limit depth that listing locks check for other locks
> -----------------------------------------------------------
>
> Key: HBASE-22386
> URL: https://issues.apache.org/jira/browse/HBASE-22386
> Project: HBase
> Issue Type: Bug
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Major
> Attachments: HBASE-22386.001.patch, HBASE-22386.002.patch
>
>
> treeWriteLock will check all the way up and down the tree for locks. This is
> more aggressive than it needs to be, and integration testing has shown that
> there's significant contention when listing tables, and this is one of
> numerous operations that doesn't need to recursively lock the whole subtree.
> There's actually a number of operations that only need to lock up or down 1
> level only, so let's start with listing: non-recursive listings don't need to
> care about what's going on more than 1 level below them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
