3 ms·
I would expect it's a database consistency issue across some distributed NoSQL store.
by JustLurking2022 4y ago
I would expect it's a database consistency issue across some distributed NoSQL store.
- hn92726819 4y agoI would imagine that's the cause too. But there are ways to prevent that. It is eventual consistency after all, right? As I mentioned in my other comment, I've had the wrong count for multiple years.