You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/07/22 19:38:00 UTC

[jira] [Commented] (GEODE-8377) User Guide: GFSH GC command should be documented to use only in non-production environments

    [ https://issues.apache.org/jira/browse/GEODE-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163031#comment-17163031 ] 

ASF subversion and git services commented on GEODE-8377:
--------------------------------------------------------

Commit 939ec631bfe59ec0c2483e8032f040acaac236bf in geode's branch refs/heads/feature/GEODE-8377 from Dave Barnes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=939ec63 ]

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
>            Priority: Major
>
> [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)