hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-17440) [0.98] Make sure DelayedClosing chore is stopped as soon as an HConnection is closed
Date Mon, 09 Jan 2017 21:36:58 GMT
Lars Hofhansl created HBASE-17440:
-------------------------------------

             Summary: [0.98] Make sure DelayedClosing chore is stopped as soon as an HConnection
is closed
                 Key: HBASE-17440
                 URL: https://issues.apache.org/jira/browse/HBASE-17440
             Project: HBase
          Issue Type: Bug
            Reporter: Lars Hofhansl
            Assignee: Lars Hofhansl


We're seeing many issue with run-away ZK client connection in long running app servers. 10k
or more send or event threads are happening frequently.

While I looked around in the code I noticed that DelayedClosing closing is not immediately
ended when an HConnection is closed, when there's an issue with HBase or ZK and client reconnect
in a tight loop, this can lead temporarily to very many threads running. These will all get
cleaned out after at most 60s, but during that time a lot of threads can be created.

The fix is a one-liner. We'll likely file other issues soon.

Interestingly branch-1 and beyond do not have this chore anymore, although - at least in branch-1
and later - I still see the ZooKeeperAliveConnection.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message