3 ms·
I feel I need to quote the post mortem back at you so you point out where I mis read the quote. "Our top focus right now is to ensure service availability. Our
by stevenwoo 9y ago
I feel I need to quote the post mortem back at you so you point out where I mis read the quote.
"Our top focus right now is to ensure service availability. Our next steps are below:
Identify and resolve the root cause of our DB performance issues. We’ve flown Mongo experts on-site to analyze our DB and usage, as well as provide real-time support during heavy load on weekends."
How does that disagree with my post?
- Thaxll 9y agoYou're implying they couldn't fix MongoDB or reached the limit which is false. In the current ( HN ) post they said they fixed it, I'm pretty sure they didn't have any experience in DBs in the first place hence why they asked for help. Nowhere in the original post they mention issues related to MongoDB itself it was probably bad design on their side.
- stevenwoo 9y agoOK I should have been clearer about my interpretation - I read flying in experts as they flew in experts from MongoDB and stumped them so that had me thinking maybe this is not possible if they stumped them. Earlier in this thread one of the engineers from MongoDB says Epic solved the issue but had not updated the blog so I was wrong about that.