geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk Lund (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (GEODE-7070) GMSMembershipManager should not manipulate AlertAppender
Date Fri, 09 Aug 2019 17:12:00 GMT

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

Kirk Lund reassigned GEODE-7070:
--------------------------------

    Assignee: Kirk Lund

> 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
>
> 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
(v7.6.14#76016)

Mime
View raw message