Yes. This check can be disabled by setting --enforce_strict_trans_tables=false on the VTTablet.
...moreAn unhappy VTTablet is one whose replication is lagging beyond the limit to which the --degraded_threshold is set. An unhappy VTTablet could still be serving queries.
VTGate will always prefer happy VTTablets over unhappy VTTablets, however if all your
...moreWe don’t have recommended thresholds as Vitess doesn’t make any functional decisions based on the statuses, beyond representing the current status in the UI. You do need to be sure to set your alerting to something lower than the threshold you choose.
...moreIf you are concerned about access security and want to change the admin user account for a given VTTablet you will need to perform the following steps:
Create the new user in the database. Give that user the required permissions. The list of what Vitess
...moreVTOrc will automatically restart replication if it is not running.
...moreSemi-sync replication enables you to prevent your primary from acknowledging a transaction to the client until a replica confirms that it has received all the changes. This adds an extra guarantee that at least one other machine has a copy of the changes.
...moreSemi-sync replication ensures data durability between the primary and at least one replica. Hardware failures are unavoidable but don't need to result in data loss if you run with semi-sync replication.
...more