[HBASE-18255] Time-Delayed HBase Performance Degradation with Java 7 - ASF JIRA

Voters

Stop watching

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: 1.3.1, 1.2.6, 1.1.11
Fix Version/s: 1.4.0, 1.3.2, 1.1.12, 1.2.7
Component/s: Performance
Labels:
- jdk7

Hadoop Flags:

Reviewed
Release Note:

Hide
This change sets the JVM property ReservedCodeCacheSize to 256MB in the provided hbase-env.sh example file. The specific value for this property attempts to prevent performance issues seen when HBase using Java 7. The value set is the same as the default when using Java8.

Show
This change sets the JVM property ReservedCodeCacheSize to 256MB in the provided hbase-env.sh example file. The specific value for this property attempts to prevent performance issues seen when HBase using Java 7. The value set is the same as the default when using Java8.

Description

The good summary of the issue and provided resolution can be found in this article:
https://community.hortonworks.com/articles/105802/time-delayed-hbase-performance-degradation-with-ja.html

In a few words, due to internal JVM 7 bug (which has been addressed only in Java 8), HotSpot code cache can become full and after that ALL JIT compilations get suspended indefinitely. The default value for code cache size in JVM 7 is quite low: 48MB. It is recommended to increase this value at least to 256MB (default in JVM 8).

This BUG affects only 1.x