> Unfortunately, this caused a new load pattern that introduced connectivity issues on the new failed-over primary, and applications were once again unable to connect to mysql1 while we worked to reset these connections.
> We were able to identify the load pattern during this incident and subsequently implemented an index to fix the main performance problem.
What actually is "load pattern" in these cases?