hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-3843) splitLogWorker starts too early
Date Mon, 02 May 2011 18:06:03 GMT

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

stack updated HBASE-3843:
-------------------------

       Resolution: Fixed
    Fix Version/s: 0.92.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

Thanks Prakash.  That makes sense.  Committed to TRUNK.

> splitLogWorker starts too early
> -------------------------------
>
>                 Key: HBASE-3843
>                 URL: https://issues.apache.org/jira/browse/HBASE-3843
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Prakash Khemani
>            Assignee: Prakash Khemani
>             Fix For: 0.92.0
>
>         Attachments: 0001-HBASE-3843-start-splitLogWorker-later-at-region-serv.patch
>
>
> splitlogworker should be started in startServiceThreads() instead of in initializeZookeeper().
This will ensure that the region server accepts a split-logging tasks only after it has successfully
done reportForDuty() to the master.

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

Mime
View raw message