Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
Hello.
We were transferring a database on one of our services, something went wrong and there was an intersection of the load on the servers. Now everything should work normally.
UPD from colleagues from operation:
There were two factors, almost independently. We started working with the Career database and, approximately in parallel, got a hard-to-diagnose problem of network connectivity. They kicked on a new database cluster (which, in the end, has nothing to do with it), on the intersection of load factors, on general crooked hands, and spent time migrating to a test one with about-old settings (which, of course, did nothing). We slept with it and in the morning found a connectivity problem almost by accident. After that, everything fell into place.
Well, he's bad. Apparently fell.
Now repaired.
The questions are doubled, apparently from the fact that someone sent his question twice, thinking that he did not go.
If there is something interesting here, then I would like to read a postmortem from the toaster / habr team.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question