You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Gray (JIRA)" <ji...@apache.org> on 2011/06/02 05:25:47 UTC
[jira] [Resolved] (HBASE-3947) SplitLog in HMaster spend long time,
move it to regionserver
[ https://issues.apache.org/jira/browse/HBASE-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Gray resolved HBASE-3947.
----------------------------------
Resolution: Duplicate
This was implemented over in HBASE-1364 and committed into trunk.
> SplitLog in HMaster spend long time, move it to regionserver
> ------------------------------------------------------------
>
> Key: HBASE-3947
> URL: https://issues.apache.org/jira/browse/HBASE-3947
> Project: HBase
> Issue Type: Improvement
> Components: master, regionserver, zookeeper
> Reporter: mingjian
> Fix For: 0.90.4
>
>
> One of our 100 nodes cluster crashed by namenode crash.
> We restarted and found it spend about two and a half hours to split hlogs.
> After crashed, there are about 3,500 hfiles in /hbase/.logs/. Split 1 of them need about 2~3 seconds.
> SplitLog works in a single thread of HMaster. Why not move it to regionservers? And HMaster only creates split plans and notifies regionserver through zookeeper.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira