[GEODE-7070] GMSMembershipManager should not manipulate AlertAppender

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Component/s: logging, membership
• Assignee: Kirk Lund
• Reporter: Kirk Lund
• Created: 09/Aug/19 17:10
• Updated: 30/Sep/19 19:09
• Resolved: 30/Sep/19 19:08

Description

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.

Issue Links

• links to: GitHub Pull Request #3904