Closed ankitthakwani closed 1 year ago
From slack thread: rerunning ISM after fixing the underlying mysql error produces a different error:
E0627 02:51:46.989567 20095 main.go:67] remote error: rpc error: code = Unknown desc = tablet ctrls-0000000100 ResetReplication failed (either fix it, or Scrap it): rpc error: code = DeadlineExceeded desc = context deadline exceeded
@GuptaManan100 is this still relevant or should we close it?
Yes, we can close it 👍
Issue: I bootstrapped a shard by initiating a tablet to be master using the command "vtctlclient -server ipmsservicemysql-ipms-v1-2021:15999 InitShardMaster -force oms_switch_unsharded/0 ctrls-100" The command failed with error but still promoted the tablet as master.
[vitess@ipmsservicemysql-ipms-v1-2021 vt]$ vttablet -version Version: bfd2ac4 (Git branch 'master') built on Wed Jun 24 12:03:05 IST 2020 by vitess@ipmsservicemysql-upi-v3-73138 using go1.14.1 linux/amd64
Steps to Reproduce the issue
STEP 1: Induce an issue by which replication will not be setup successfully, here I am setting up the password with length >32 character(limit for MySQL replication) Set up a vitess keyspace with 3 replica tablets.
STEP 2: Elect a tablet as master from one of the three replica tablets
STEP 3: Observe that even though the InitShardMaster failed, the tablet is marked as master
VTCTLD LOGS
VTTABLET Replica LOGS
VTTABLET MASTER LOGS