You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2019/08/08 14:41:00 UTC
[jira] [Resolved] (HBASE-22821) The application get stuck when put
data to hbase table
[ https://issues.apache.org/jira/browse/HBASE-22821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Busbey resolved HBASE-22821.
---------------------------------
Resolution: Invalid
please bring these kinds of questions to the [user@hbase.apache.org|mailto:user@hbase.apache.org] mailing list:
[http://hbase.apache.org/mail-lists.html]
> The application get stuck when put data to hbase table
> ------------------------------------------------------
>
> Key: HBASE-22821
> URL: https://issues.apache.org/jira/browse/HBASE-22821
> Project: HBase
> Issue Type: Test
> Components: Client
> Affects Versions: 1.0.0
> Reporter: jay
> Priority: Major
>
> About several days ago, I found one issue that the application get stuck when I put data to hbase. When I check the log, I found 2 question, one is like
> " #22349, waiting for some tasks to finish. Expected max=0, tasksInProgress=76" and "WARN - #22348, not sent: 1 operations, node1,60020,1529589908290" followed by java.lang.InterruptedException: sleep interrupted, and I did not find any another exception. I don not know why it get stuck. Is it deadlock? And another question is why the "sleep interrupted" exception happened? See the following code:
> try {
> Thread.sleep(backOffTime);
> } catch (InterruptedException e) {
> LOG.warn("#" + id + ", not sent: " + toReplay.size() + " operations, " + oldServer, e);
> Thread.currentThread().interrupt();
> return;
> }
> As fa as I know, the InterruptedException will happen only when the thead is called interrupt() method or the pool which the thead belongs is shutdown. But I searched the all the code of the project, I did not find any interrupt() method. And I think it is impossible that the pool is shut down before the thread finish. So anybody can help me solve this issue?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)