cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaydeepkumar Chovatia (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-14527) Real time bad query logging framework
Date Wed, 20 Jun 2018 04:32:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jaydeepkumar Chovatia updated CASSANDRA-14527:
----------------------------------------------
    Summary: Real time bad query logging framework  (was: Real time Bad query logging framework)

> Real time bad query logging framework
> -------------------------------------
>
>                 Key: CASSANDRA-14527
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14527
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Observability
>            Reporter: Jaydeepkumar Chovatia
>            Assignee: Jaydeepkumar Chovatia
>            Priority: Major
>             Fix For: 4.x
>
>
> Debugging Cassandra performance problems in really large production environment with
different workload involves lots of challenges. There are different types of problems caused
by queries, but major problem is there is only a little information available from Cassandra
to diagnose performance issues.Most of the times user/ops team is ready to take actions on
queries provided Cassandra provides more details on different problems seen at server side.
> There has been already lots of work done as part of CASSANDRA-12403, [large partition
warning |https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/big/BigTableWriter.java#L208],
[tombstone warning |https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ReadCommand.java#L490]
but I think Cassandra needs to provide more concrete information, tunable parameters, tunable
way to consume this info, etc. Hence this jira is to have some common way of detecting and
logging different problems in Cassandra cluster which could have potential impact on Cassandra
cluster performance.
> 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. 
> Please visit this document which has details like what is currently available, motivation
behind developing this common framework, architecture, samples, etc. [https://docs.google.com/document/d/1D0HNjC3a7gnuKnR_iDXLI5mvn1zQxtV7tloMaLYIENE/edit?usp=sharing]
> Here is the patch with this feature:
> ||trunk||
> |[!https://circleci.com/gh/jaydeepkumar1984/cassandra/tree/bqr.svg?style=svg! |https://circleci.com/gh/jaydeepkumar1984/cassandra/82]|
> |[patch |https://github.com/apache/cassandra/compare/trunk...jaydeepkumar1984:bqr]|
> Please review this doc/patch and provide your feedback.
> Thank you!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message