Considering the Use of LifeKeeper I-O Fencing

Since the shared disk environment cannot be used in an AWS environment, you cannot use SCSI reservations to prevent a split-brain. IP resources may cause a split-brain as it uses the real IP resource with different IP addresses for each node.

For this reason, please consider the use of Quorum/Witness server or STONITH, an I/O fencing function of LifeKeeper to use this configuration safely.

Since you can implement I/O fencing separately without the Quorum server, if you use the TCP_REMOTE setting in Quorum mode, it is easy to implement in the cloud environment. For more details, please refer to the following:

AWS Direct Connect Known Issues and Troubleshooting

There are currently no Known Issues.

フィードバック

フィードバックありがとうございました

このトピックへフィードバック

送信