[JBPAPP-9562] JGroups FLUSH failure logging does not show which member(s) are at fault - JBoss Issue Tracker

XML

Word

Printable

Affects:

Release Notes
Release Notes Text:

Hide
When a cluster member does not respond before timeout, other members can fail to join the cluster. Previously, in this case, the logs contained only an entry about the timeout event that occurred while waiting for responses from the cluster ("GMS flush by coordinator at <ip_address>:<port> failed ") and did not report which members were not present in the cluster. Now, the log level of this event was changed from DEBUG to WARN, and the log event contains a list of the missing cluster members to allow easier troubleshooting.

Show
When a cluster member does not respond before timeout, other members can fail to join the cluster. Previously, in this case, the logs contained only an entry about the timeout event that occurred while waiting for responses from the cluster ("GMS flush by coordinator at <ip_address>:<port> failed ") and did not report which members were not present in the cluster. Now, the log level of this event was changed from DEBUG to WARN, and the log event contains a list of the missing cluster members to allow easier troubleshooting.
Release Notes Docs Status:
Documented as Feature Request
Docs QE Status:
NEW

When FLUSH fails to get responses from all members, it logs:

GMS flush by coordinator at <ip_address>:<port> failed

It should log which members did not respond, to aid in troubleshooting the cluster.

is blocked by

JGRP-1494 FLUSH failure logging does not show which member(s) are at fault