Restore strategy

In K8s, MySQL replica pod might restart due to various reasons. When it is coming up, how do we decide, whether to restore or not? Any guidelines?

What kind of setup you are using, is it cluster or stand alone ?
if its stand alone than there is no need to restore until its DB is corrupted and if its cluster than it should join back to cluster when its come back

1 Like

@erpramodprajapat Thanks.

Cluster Mode. If we have GBs of Data, how do we know that the DB is in right state?. Bcoz if there is any issue, then manual/automatic intervention needed to bring back to right state. Due to the size of data, Sync up of full data from Master might not be the solution. How to find (automatic/ manual) and handle the restore?