[
https://issues.apache.org/jira/browse/ZOOKEEPER-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153309#comment-13153309
]
Sean Carr commented on ZOOKEEPER-545:
-------------------------------------
This seems like a simple issue to resolve and then maybe improve upon later if
there is uncertainty as to what the ideal options are. I recently spent a lot
of time debugging some nasty production application problems that ended up
being a result of long GC pauses in ZooKeeper since ConcMarkSweep is not the
default (and I assumed it would be) combined with ZOOKEEPER-706.
I haven't tested CMSIncrementalMode a bunch but making at least
UseConcMarkSweepGC the default in the start script seems like an important,
low-risk change.
> investigate use of realtime gc as the recommened default for server vm
> ----------------------------------------------------------------------
>
> Key: ZOOKEEPER-545
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-545
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Patrick Hunt
> Priority: Critical
> Fix For: 3.5.0
>
>
> We currently don't recommend that ppl use the realtime gc when running the
> server, we probably should.
> Before we do so we need to verify that it works.
> We should make it the default for all our tests.
> concurrent vs "g2" or whatever it's called (new in 1.6_15 or something?)
> Update all scripts to specify this option
> update documentation to include this option and add section in the dev/ops
> docs detailing it's benefits (in particular latency effects of gc)
> Also, -server option? any benefit for us to recommend this as well?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
