5 ms·
> Unfortunately, this caused a new load pattern that introduced connectivity issues on the new failed-over primary, and applications were once again unable to c
by yla92 5y ago
> 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?
- EricE 5y agoProbably cascading failures - that's certainly an unhealthy pattern of loads. One part of the house of cards collapses putting previously unseen pressure on another part of the house of cards - that then promptly collapses - so forth and so on. Technical debt - here's a real world example of what those words really mean!