The memory footprint of "corosync" process increases when it has communication problems with the other cluster Nodes
This document (7022840) is provided subject to the disclaimer at the end of this document.
2018-02-27T13:52:10.477274+11:00 Node1 corosync: [TOTEM ] A processor failed, forming new configuration.
2018-02-27T13:52:12.549516+11:00 Node1 corosync: [TOTEM ] A new membership (10.0.9.13:75200) was formed. Members left: 2
2018-02-27T13:52:12.549919+11:00 Node1 corosync: [TOTEM ] Failed to receive the leave message. failed: 2
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7022840
- Creation Date: 11-Apr-2018
- Modified Date:03-Mar-2020
- SUSE Linux Enterprise High Availability Extension
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com