[ https://issues.apache.org/jira/browse/GEODE-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163726#comment-17163726 ]
ASF subversion and git services commented on GEODE-8377: -------------------------------------------------------- Commit dcbe8dedb004c64e0b8812293e2220763447b061 in geode's branch refs/heads/support/1.13 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dcbe8de ] GEODE-8377: User Guide: GFSH GC command should be documented ... (#5396) * GEODE-8377: User Guide: GFSH GC command should be documented to use only in non-production environments > User Guide: GFSH GC command should be documented to use only in > non-production environments > ------------------------------------------------------------------------------------------- > > Key: GEODE-8377 > URL: https://issues.apache.org/jira/browse/GEODE-8377 > Project: Geode > Issue Type: Improvement > Components: docs > Reporter: Dave Barnes > Assignee: Dave Barnes > Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > [DWisler] The GSFH GC command is very likely to cause members of GemFire to > be kicked out due to being unresponsive, as this is a forced GC event and not > always handled well by GC outside of normal GC processing. We need to > document that this should only be used in non-production environments, and to > not use it if it causes such issues. We are especially susceptible if > multiple members run on the same vm/host and/or if the number of cpus is > insufficient to handle the “load” needed by GC. -- This message was sent by Atlassian Jira (v8.3.4#803005)