You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "ryan rawson (JIRA)" <ji...@apache.org> on 2009/04/17 09:54:15 UTC
[jira] Created: (HBASE-1326) hbase doesn't size memcache correctly
under -XX:+UseG1GC
hbase doesn't size memcache correctly under -XX:+UseG1GC
--------------------------------------------------------
Key: HBASE-1326
URL: https://issues.apache.org/jira/browse/HBASE-1326
Project: Hadoop HBase
Issue Type: Bug
Affects Versions: 0.20.0
Environment: java 1.7
Reporter: ryan rawson
Fix For: 0.20.0
I get this in the logfile:
2009-04-16 23:49:20,518 INFO org.apache.hadoop.hbase.regionserver.MemcacheFlusher: Forced flushing of <table redacted>,1239954535262 because global memcache limit of 3.2m exceeded; currently 3.2m and flushing till 2.0m
With the experimental G1 GC, the heap size is created differently, and the way we calculate the size of memcache is flawed under this GC. This affects performance and makes things reallll slow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1326) hbase doesn't size memcache
correctly under -XX:+UseG1GC
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702599#action_12702599 ]
stack commented on HBASE-1326:
------------------------------
Setting -Xms helped, right Ryan? Its how we're using what comes back from the MXBean?
> hbase doesn't size memcache correctly under -XX:+UseG1GC
> --------------------------------------------------------
>
> Key: HBASE-1326
> URL: https://issues.apache.org/jira/browse/HBASE-1326
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.0
> Environment: java 1.7
> Reporter: ryan rawson
> Fix For: 0.20.0
>
>
> I get this in the logfile:
> 2009-04-16 23:49:20,518 INFO org.apache.hadoop.hbase.regionserver.MemcacheFlusher: Forced flushing of <table redacted>,1239954535262 because global memcache limit of 3.2m exceeded; currently 3.2m and flushing till 2.0m
> With the experimental G1 GC, the heap size is created differently, and the way we calculate the size of memcache is flawed under this GC. This affects performance and makes things reallll slow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-1326) hbase doesn't size memcache correctly
under -XX:+UseG1GC
Posted by "ryan rawson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ryan rawson resolved HBASE-1326.
--------------------------------
Resolution: Invalid
JVM bug, to workaround set -Xms
> hbase doesn't size memcache correctly under -XX:+UseG1GC
> --------------------------------------------------------
>
> Key: HBASE-1326
> URL: https://issues.apache.org/jira/browse/HBASE-1326
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.0
> Environment: java 1.7
> Reporter: ryan rawson
> Fix For: 0.20.0
>
>
> I get this in the logfile:
> 2009-04-16 23:49:20,518 INFO org.apache.hadoop.hbase.regionserver.MemcacheFlusher: Forced flushing of <table redacted>,1239954535262 because global memcache limit of 3.2m exceeded; currently 3.2m and flushing till 2.0m
> With the experimental G1 GC, the heap size is created differently, and the way we calculate the size of memcache is flawed under this GC. This affects performance and makes things reallll slow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.