[ https://issues.apache.org/jira/browse/HBASE-10500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-10500: --------------------------------- Description: Running {{hbck --repair}} when BucketCache is enabled in offheap mode can cause OOM. This is apparently because {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for hbck. It instantiates an HRegion instance as part of HDFSIntegrityFixer.handleHoleInRegionChain. That HRegion initializes its CacheConfig, which doesn't have the necessary Direct Memory. Possible solutions include: - disable blockcache in the config used by hbck when running its repairs - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments I'm leaning toward the former because it's possible that hbck is run on a host with different hardware profile as the RS. was: Running {{hbck --repair}} when BucketCache is enabled in offheap mode can cause OOM. This is apparently because {{bin/hbase}} does not include $HBASE_REGIONSERVER_OPTS for hbck. It instantiates an HRegion instance as part of HDFSIntegrityFixer.handleHoleInRegionChain. That HRegion initializes its CacheConfig, which doesn't have the necessary Direct Memory. Possible solutions include: - disable blockcache in the config used by hbck when running its repairs - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments I'm leaning toward the former because it's possible that hbck is run on a host with the same hardware profile as the RS. > hbck and OOM when BucketCache is enabled > ---------------------------------------- > > Key: HBASE-10500 > URL: https://issues.apache.org/jira/browse/HBASE-10500 > Project: HBase > Issue Type: Bug > Components: hbck > Affects Versions: 0.98.0 > Reporter: Nick Dimiduk > Assignee: Nick Dimiduk > > Running {{hbck --repair}} when BucketCache is enabled in offheap mode can > cause OOM. This is apparently because {{bin/hbase}} does not include > $HBASE_REGIONSERVER_OPTS for hbck. It instantiates an HRegion instance as > part of HDFSIntegrityFixer.handleHoleInRegionChain. That HRegion initializes > its CacheConfig, which doesn't have the necessary Direct Memory. > Possible solutions include: > - disable blockcache in the config used by hbck when running its repairs > - include HBASE_REGIONSERVER_OPTS in the HBaseFSCK startup arguments > I'm leaning toward the former because it's possible that hbck is run on a > host with different hardware profile as the RS. -- This message was sent by Atlassian JIRA (v6.1.5#6160)