You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Kirk Lund (Jira)" <ji...@apache.org> on 2019/09/30 19:09:00 UTC

[jira] [Resolved] (GEODE-7070) GMSMembershipManager should not manipulate AlertAppender

     [ https://issues.apache.org/jira/browse/GEODE-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk Lund resolved GEODE-7070.
------------------------------
    Resolution: Invalid

> GMSMembershipManager should not manipulate AlertAppender
> --------------------------------------------------------
>
>                 Key: GEODE-7070
>                 URL: https://issues.apache.org/jira/browse/GEODE-7070
>             Project: Geode
>          Issue Type: Wish
>          Components: logging, membership
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> GMSMembershipManager should not manipulate AlertAppender.
> AlertAppender will be moving to geode-log4j and will not be available for direct access from GMSMembershipManager. Also, if GMSMembershipManager really needs to stop the alerting session (which is not obvious), it should notify the InternalDistributedSystem that it is initiating forceDisconnect and then IDS would stop alerting via its AlertingSession field.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)