Bug Report: replicas do not self heal when replication initialization fails

[GuptaManan100]

Overview of the Issue

Sometimes MySQL replication isn't initialized properly due to a crash or corrupted file writes, etc.

This causes START REPLICA command to not being able to start replication -

mysql> start replica;
ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the MySQL error log

mysql> select * from performance_schema.error_log order by logged desc limit 1;
+----------------------------+-----------+-------+------------+-----------+------------------------------------------------------------------------------------------------------+
| LOGGED                     | THREAD_ID | PRIO  | ERROR_CODE | SUBSYSTEM | DATA                                                                                                 |
+----------------------------+-----------+-------+------------+-----------+------------------------------------------------------------------------------------------------------+
| 2022-02-07 17:32:58.104853 |        48 | Error | MY-010575  | Repl      | Error looking for file after /vt/vtdataroot/vt_2107724286/relay-logs/vt-2107724286-relay-bin.000001. |
+----------------------------+-----------+-------+------------+-----------+------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)

Even though the replication manager and VTOrc pick up that the replication is not running on this tablet in question, they aren't able to repair it since START REPLICA keeps failing.

Reproduction Steps

Bring up tablets multiple times until a failure in replication like this is encountered.

Binary Version

main and all previous releases too

Operating System and Environment details

-

Log Fragments

No response