hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4247) Add isAborted method to the Abortable interface
Date Sun, 28 Aug 2011 16:00:37 GMT

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

Ted Yu commented on HBASE-4247:
-------------------------------

According to the javadoc for Abortable:
{noformat}
 * This is used primarily for ZooKeeper usage when we could get an unexpected
 * and fatal exception, requiring an abort.
{noformat}
This means the first if block in the above abort() method is supposed to handle almost all
calls to the method.

To try to validate the above judgement, I issued the following two searches among all test
output files:
{code}
grep FATAL target/surefire-reports/* | grep ConnectionManager | grep -v TestMergeTool
grep 'Could not reconnect to ZooKeeper after session' target/surefire-reports/*
{code}
There was nothing returned.

TestMergeTool is a special case where HBase cluster is supposed to be unavailable.

Looking at getMaster() and locateRegion(), this.closed being true would make them return immediately.

Hope this helps with your question.

> Add isAborted method to the Abortable interface
> -----------------------------------------------
>
>                 Key: HBASE-4247
>                 URL: https://issues.apache.org/jira/browse/HBASE-4247
>             Project: HBase
>          Issue Type: Task
>            Reporter: Akash Ashok
>            Assignee: Akash Ashok
>            Priority: Minor
>             Fix For: 0.94.0
>
>
> Add a new method isAborted() to the Abortable interface 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message