Re: Real time bad query logging framework in C*
Jaydeep, thanks for taking this discussion to the dev list. I think it's
the best place to introduce new idea, discuss them in general and how
they potentially fit in. As already mention in the ticket, I do share
your assessment that we should try to improve making operational issue
more visible to users. We already provide tons of metrics and provide
some useful logging (e.g. when reading too many tombstones), but I think
we should still be able to implement further checks in-code that
highlight potentially issues. Maybe we could really use a framework for
that, I don't know.
If you followed the discussions a while ago, we also talked about moving
some of the code out of Cassandra into side-car processes. Although this
will likely not manifest for 4.0, most of the devs seem to be fond of
the idea and so am I. Not wanting to derail this discussion (about your
proposed solution), but let me just briefly mention that I've been
working on some related approach (diagnostic events, CASSANDRA-12944),
which would allow to expose internal events to external processes that
would be able to analyze these events, alert users, or event act on
them. It's a different approach from what you're suggesting, but just
wanted to mention this and maybe you'd agree that having external
processes for monitoring Cassandra has some advantages.
On 20.06.2018 06:33, Jaydeep Chovatia wrote:
> We have worked on developing some common framework to detect/log
> anti-patterns/bad queries in Cassandra. Target for this effort would be
> to reduce burden on ops to handle Cassandra at large scale, as well as
> help beginners to quickly identify performance problems with the Cassandra.
> Initially we wanted to try out to make sure it really works and provides
> value. we've opened JIRA with all the details. Would you please review and
> provide your feedback on this effort?
> Thank You!!!
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxxxx