4 ms·
First, that bug is closed. Second, the last comment has nothing to do with TSM. Just because a user thinks it's related to the storage engine and posts that, do
by pauldix 11y ago
First, that bug is closed. Second, the last comment has nothing to do with TSM. Just because a user thinks it's related to the storage engine and posts that, doesn't mean that's what is actually happening.
For that particular user, it is something else they're hitting. Without more info we have no way of knowing why they're hitting that error.
Either I'm lying about people using this thing at significant scale or that user is having some other problem. Put simply, TSM is well tested and works. I'm certain other bugs will come up but the comment you linked has nothing to do with TSM.
I should also note that we have users running Telegraf on thousands of hosts sending metrics to a standalone InfluxDB server.
- kev009 11y agoYou're not lying, you're cherry picking cases that support your company's growth and ignoring the reality of bug volume on github and user reports of it not working well at moderate scale. I have no stake whether you get it together or flop, so from this perspective I will cherry-pick bugs because that is what matters to users of a database which should be boring, stable, reliable, efficient. With the change of direction on clustering, and I am skeptic of that being done well any time soon given the storage engine history, you have a hard road ahead of you. Until/unless you get it together, there are better choices, especially for pay, and the "everything is fine" message is infuriating. Also, despite being mean here I do hope you get it together. I just wish you'd reconsider the marketing approach and hold claims of a production release back a long time until the bugs are under control.