You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2016/03/10 00:00:42 UTC
[jira] [Commented] (HBASE-15436) BufferedMutatorImpl.flush()
appears to get stuck
[ https://issues.apache.org/jira/browse/HBASE-15436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188261#comment-15188261 ]
Sangjin Lee commented on HBASE-15436:
-------------------------------------
See YARN-4736 for more details.
> BufferedMutatorImpl.flush() appears to get stuck
> ------------------------------------------------
>
> Key: HBASE-15436
> URL: https://issues.apache.org/jira/browse/HBASE-15436
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.0.2
> Reporter: Sangjin Lee
> Attachments: hbaseException.log, threaddump.log
>
>
> We noticed an instance where the thread that was executing a flush ({{BufferedMutatorImpl.flush()}}) got stuck when the (local one-node) cluster shut down and was unable to get out of that stuck state.
> The setup is a single node HBase cluster, and apparently the cluster went away when the client was executing flush. The flush eventually logged a failure after 30+ minutes of retrying. That is understandable.
> What is unexpected is that thread is stuck in this state (i.e. in the {{flush()}} call). I would have expected the {{flush()}} call to return after the complete failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)