Sangjin Lee created HBASE-15436:
-----------------------------------
Summary: 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
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)