Pivotal Knowledge Base

Follow

Previous versions of ERT and P-MySQL scaretext incorrectly direct Operator to bootstrap

Environment

Pivotal Cloud Foundry

MySQL for Pivotal Cloud Foundry

Purpose

When implementing the scaretext produced by the Interruptor, you run the bootstrap errand. Unfortunately, bootstrap is the wrong errand to use here.

WSREP_SST: [ERROR] ############################################################################## (20170530 15:29:27.283)
WSREP_SST: [ERROR] SST disabled due to danger of data loss. Verify data and bootstrap the cluster (20170530 15:29:27.285)
WSREP_SST: [ERROR] ############################################################################## (20170530 15:29:27.287)

Cause

The errand, in this case, is supposed to be rejoin-unsafe. Bootstrapping the cluster will, in some cases, make the problem worse.

Resolution

The fix for this problem was to change bootstrap to rejoin-unsafe

The scaretext error was corrected in the following versions: 

Screen_Shot_2017-06-26_at_12.06.57_PM.png

You can refer to the Pivotal Cloud Foundry docs 1.9, 1.8, and 1.7, for further details about this change. 

Comments

Powered by Zendesk