You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2013/02/22 12:12:12 UTC

[jira] [Commented] (HBASE-7906) OfflineCallBack in bulk assignment does not work as expected

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

ramkrishna.s.vasudevan commented on HBASE-7906:
-----------------------------------------------

So if we want async behaviour then we cannot find if the znode exists or not.
Even if it exists we should take some action on that.  May be we should forcefully set the state to OFFLINE or we may have to abort the server.
But for doing it we may have to read the data of the znode.

So can we introduce a config to say if it is ok to check the data and then asynchronously create znode in OFFLINE state.  Because as Jimmy pointed out in HBASE-7799 this piece of code is aimed at faster execution and hence the async nature.

Any other suggestions on this?
                
> OfflineCallBack in bulk assignment does not work as expected
> ------------------------------------------------------------
>
>                 Key: HBASE-7906
>                 URL: https://issues.apache.org/jira/browse/HBASE-7906
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>
> This is as part of discussion in HBASE-7799.
> The OfflineCallBack does not bother if the znode already exists or not.  Infact the catch block AM.asyncSetOfflineInZooKeeper() is a dead code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira