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

Posted to issues@hbase.apache.org by "rajeshbabu (JIRA)" <ji...@apache.org> on 2013/03/17 11:26:12 UTC

[jira] [Updated] (HBASE-8130) initialize TableLockManager before initializing AssignmentManager

     [ https://issues.apache.org/jira/browse/HBASE-8130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

rajeshbabu updated HBASE-8130:
------------------------------

    Summary: initialize TableLockManager before initializing AssignmentManager  (was: initialize TableLocalManager before initializing AssignmentManager)
    
> initialize TableLockManager before initializing AssignmentManager
> -----------------------------------------------------------------
>
>                 Key: HBASE-8130
>                 URL: https://issues.apache.org/jira/browse/HBASE-8130
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.95.0
>            Reporter: rajeshbabu
>            Assignee: rajeshbabu
>             Fix For: 0.98.0
>
>
> Getting NullPointerException while recovering disabling/enabling tables in AM.
> AM.tableLockManager is not pointing to HM.tableLockManager initalized after AM initialization.So its always null.

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