hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15436) BufferedMutatorImpl.flush() appears to get stuck
Date Wed, 16 Mar 2016 04:07:33 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196723#comment-15196723
] 

Anoop Sam John commented on HBASE-15436:
----------------------------------------

When close() is called on BufferedMutator what is the expectation? All the prior writes (async)
should get synced with HBase RS?
Ya when data is pumped in in async way, it is expected that there may be data loss. If client
went down abruptly.  So we can say if close is called, we can try flush data and gracefully
down. If flush is not happening normally  we may need to close it with out flush of remaining
mutations (?)  How abt the decision making?  cc [~tedyu]

> 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)

Mime
View raw message