[
https://issues.apache.org/jira/browse/HBASE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1683:
-------------------------
Attachment: 1683.patch
On pset cluster, we ran into this issue though master had 2G heap.
As a (poor) workaround, I set down the default readers/writers during split
from 10 to a conservative 3 and added facililty to influence this number if
wanted rather than have the values hardcoded.
> OOME on master splitting logs; stuck, won't go down
> ---------------------------------------------------
>
> Key: HBASE-1683
> URL: https://issues.apache.org/jira/browse/HBASE-1683
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.20.0
>
> Attachments: 1683.patch
>
>
> This is holding it up.
> {code}
> "HMaster" prio=10 tid=0x000000004048c000 nid=0x6ab0 in Object.wait()
> [0x0000000040d6c000..0x0000000040d6cd00]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Unknown Source)
> - locked <0x00007fc6d28be720> (a
> org.apache.hadoop.hbase.master.RootScanner)
> at java.lang.Thread.join(Unknown Source)
> at
> org.apache.hadoop.hbase.master.RegionManager.stop(RegionManager.java:611)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:405)
> {code}
> Was splitting 11 logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
