You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2012/10/09 22:14:02 UTC
[jira] [Created] (ACCUMULO-798) large ParNew can cause long-term
stop-the-world java GC
Eric Newton created ACCUMULO-798:
------------------------------------
Summary: large ParNew can cause long-term stop-the-world java GC
Key: ACCUMULO-798
URL: https://issues.apache.org/jira/browse/ACCUMULO-798
Project: Accumulo
Issue Type: Bug
Components: tserver
Affects Versions: 1.4.1
Environment: running a tserver with a very large memory foot-print (16G)
Reporter: Eric Newton
Assignee: Keith Turner
Priority: Trivial
Fix For: 1.4.2
While running a tserver with 16G of JVM memory, under continuous ingest, a ParNew collection took longer than 40 seconds. This happened on two different servers (out of 40) after performing continuous ingest for more than 20 hours.
Limiting the ParNew generation to 2G, and never saw this failure again.
Recommend this setting in the examples, even though none of the examples approaches this memory size.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ACCUMULO-798) large ParNew can cause long-term
stop-the-world java GC
Posted by "Eric Newton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Newton resolved ACCUMULO-798.
----------------------------------
Resolution: Fixed
fixed in r1396758 for 1.4 and r1396760 in 1.5 (trunk)
> large ParNew can cause long-term stop-the-world java GC
> -------------------------------------------------------
>
> Key: ACCUMULO-798
> URL: https://issues.apache.org/jira/browse/ACCUMULO-798
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.4.1
> Environment: running a tserver with a very large memory foot-print (16G)
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Trivial
> Fix For: 1.4.2
>
>
> While running a tserver with 16G of JVM memory, under continuous ingest, a ParNew collection took longer than 40 seconds. This happened on two different servers (out of 40) after performing continuous ingest for more than 20 hours.
> Limiting the ParNew generation to 2G, and never saw this failure again.
> Recommend this setting in the examples, even though none of the examples approaches this memory size.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (ACCUMULO-798) large ParNew can cause long-term
stop-the-world java GC
Posted by "Eric Newton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Newton reassigned ACCUMULO-798:
------------------------------------
Assignee: Eric Newton (was: Keith Turner)
> large ParNew can cause long-term stop-the-world java GC
> -------------------------------------------------------
>
> Key: ACCUMULO-798
> URL: https://issues.apache.org/jira/browse/ACCUMULO-798
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.4.1
> Environment: running a tserver with a very large memory foot-print (16G)
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Trivial
> Fix For: 1.4.2
>
>
> While running a tserver with 16G of JVM memory, under continuous ingest, a ParNew collection took longer than 40 seconds. This happened on two different servers (out of 40) after performing continuous ingest for more than 20 hours.
> Limiting the ParNew generation to 2G, and never saw this failure again.
> Recommend this setting in the examples, even though none of the examples approaches this memory size.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira