[jira] [Updated] (CASSANDRA-14527) Real time bad query logging framework
[ 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework
[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: 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! was: 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 Jira is to reduce burden on ops, 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! > 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
[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework
[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: 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 Jira is to reduce burden on ops, 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! was: 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. Also this Jira will be useful for the 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! > 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 >
[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework
[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: 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. Also this Jira will be useful for the 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! was: 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. 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! > 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 >
[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework
[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: 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. 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! was: If Cassandra is not used in right way then it can create adverse effect to the application. There are lots of bad queries when using Cassandra, but major problem is end user don’t know where and what exactly is the problem. Most of the times end user is ready to take actions on bad queries provided Cassandra gives all detailed which could have potential impact on cluster performance. There has been already lots of work done as part of CASSANDRA-12403, proposal as part of this JIRA is let’s have some common way of detecting and logging different problems in Cassandra cluster which could have potential impact on Cassandra cluster performance. 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 and the patch, and provide your opinion and feedback about this effort. Thank you! > 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. > Please visit this document which has details like what is currently > available, motivation behind developing this common framework,
[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework
[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Podkowinski updated CASSANDRA-14527: --- Fix Version/s: (was: 4.0) 4.x > 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 > > > If Cassandra is not used in right way then it can create adverse effect to > the application. There are lots of bad queries when using Cassandra, but > major problem is end user don’t know where and what exactly is the problem. > Most of the times end user is ready to take actions on bad queries provided > Cassandra gives all detailed which could have potential impact on cluster > performance. > There has been already lots of work done as part of CASSANDRA-12403, proposal > as part of this JIRA is let’s have some common way of detecting and logging > different problems in Cassandra cluster which could have potential impact on > Cassandra cluster performance. > 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 and the patch, and provide your opinion and feedback > about this effort. > Thank you! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework
[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: If Cassandra is not used in right way then it can create adverse effect to the application. There are lots of bad queries when using Cassandra, but major problem is end user don’t know where and what exactly is the problem. Most of the times end user is ready to take actions on bad queries provided Cassandra gives all detailed which could have potential impact on cluster performance. There has been already lots of work done as part of CASSANDRA-12403, proposal as part of this JIRA is let’s have some common way of detecting and logging different problems in Cassandra cluster which could have potential impact on Cassandra cluster performance. 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 and the patch, and provide your opinion and feedback about this effort. Thank you! was: If Cassandra is not used in right way then it can create adverse effect to the application. There are lots of bad queries when using Cassandra, but major problem is end user don’t know where and what exactly is the problem. Most of the times end user is ready to take actions on bad queries provided Cassandra gives all detailed which could have potential impact on cluster performance. There has been already lots of work done as part of CASSANDRA-12403, proposal as part of this JIRA is let’s have some common way of detecting and logging different problems in Cassandra cluster which could have potential impact on Cassandra cluster performance. 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/81]| |[patch |https://github.com/apache/cassandra/compare/trunk...jaydeepkumar1984:bqr]| Please review this doc and the patch, and provide your opinion and feedback about this effort. Thank you! > 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.0 > > > If Cassandra is not used in right way then it can create adverse effect to > the application. There are lots of bad queries when using Cassandra, but > major problem is end user don’t know where and what exactly is the problem. > Most of the times end user is ready to take actions on bad queries provided > Cassandra gives all detailed which could have potential impact on cluster > performance. > There has been already lots of work done as part of CASSANDRA-12403, proposal > as part of this JIRA is let’s have some common way of detecting and logging > different problems in Cassandra cluster which could have potential impact on > Cassandra cluster performance. > 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 and the patch, and provide your opinion and feedback > about this effort. > Thank you! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework
[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: If Cassandra is not used in right way then it can create adverse effect to the application. There are lots of bad queries when using Cassandra, but major problem is end user don’t know where and what exactly is the problem. Most of the times end user is ready to take actions on bad queries provided Cassandra gives all detailed which could have potential impact on cluster performance. There has been already lots of work done as part of CASSANDRA-12403, proposal as part of this JIRA is let’s have some common way of detecting and logging different problems in Cassandra cluster which could have potential impact on Cassandra cluster performance. 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/81]| |[patch |https://github.com/apache/cassandra/compare/trunk...jaydeepkumar1984:bqr]| Please review this doc and the patch, and provide your opinion and feedback about this effort. Thank you! was: If Cassandra is not used in right way then it can create adverse effect to the application. There are lots of bad queries when using Cassandra, but major problem is end user don’t know where and what exactly is the problem. Most of the times end user is ready to take actions on bad queries provided Cassandra gives all detailed which could have potential impact on cluster performance. There has been already lots of work done as part of CASSANDRA-12403, proposal as part of this JIRA is let’s have some common way of detecting and logging different problems in Cassandra cluster which could have potential impact on Cassandra cluster performance. 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/78]| |[patch |https://github.com/apache/cassandra/compare/trunk...jaydeepkumar1984:bqr]| Please review this doc and the patch, and provide your opinion and feedback about this effort. Thank you! > 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.0 > > > If Cassandra is not used in right way then it can create adverse effect to > the application. There are lots of bad queries when using Cassandra, but > major problem is end user don’t know where and what exactly is the problem. > Most of the times end user is ready to take actions on bad queries provided > Cassandra gives all detailed which could have potential impact on cluster > performance. > There has been already lots of work done as part of CASSANDRA-12403, proposal > as part of this JIRA is let’s have some common way of detecting and logging > different problems in Cassandra cluster which could have potential impact on > Cassandra cluster performance. > 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/81]| > |[patch > |https://github.com/apache/cassandra/compare/trunk...jaydeepkumar1984:bqr]| > Please review this doc and the patch, and provide your opinion and feedback > about this effort. > Thank you! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
