[jira] [Comment Edited] (CASSANDRA-9191) Log and count failure to obtain requested consistency
[ https://issues.apache.org/jira/browse/CASSANDRA-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554578#comment-15554578 ] Christopher Bradford edited comment on CASSANDRA-9191 at 10/7/16 8:59 AM: -- Do we only want the query displayed in the debug log or the tracing as well? This snippet is pulled from the read path, are you looking for this message when the requested CL is not achieved during a write operation? was (Author: bradfordcp): Do we only want the query displayed in the debug log or the tracing as well? This is pulled from the read path, are you looking for this message when the requested CL is not achieved during a write operation? > Log and count failure to obtain requested consistency > - > > Key: CASSANDRA-9191 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9191 > Project: Cassandra > Issue Type: Improvement >Reporter: Matt Stump >Priority: Minor > Labels: lhf > > Cassandra should have a way to log failed requests due to failure to obtain > requested consistency. This should be logged as error or warning by default. > Also exposed should be a counter for the benefit of opscenter. > Currently the only way to log this is at the client. Often the application > and DB teams are separate and it's very difficult to obtain client logs. Also > because it's only visible to the client no visibility is given to opscenter > making it difficult for the field to track down or isolate systematic or node > level errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-9191) Log and count failure to obtain requested consistency
[ https://issues.apache.org/jira/browse/CASSANDRA-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14495166#comment-14495166 ] Matt Stump edited comment on CASSANDRA-9191 at 4/14/15 11:49 PM: - Histograms don't provide the data granularity I'm looking for. I want the actual statement. I was on a call today where I'm told statements are failing due to consistency failure and I'm given no access to developers or access to code. I'm ok with the feature being off by default as long as I can turn it on via nodetool. Either that or give me the swiss army knife that is CASSANDRA-9193. was (Author: mstump): Histograms don't provide the data granularity I'm looking for. I want the actual statement. I was on a call today where I'm told statements are failing due to consistency failure and I'm given no access to developers or access to code. I'm ok with the feature being off by default as long as I can turn it on via nodetool. Either that or give me the swiss army knife that is #9193. Log and count failure to obtain requested consistency - Key: CASSANDRA-9191 URL: https://issues.apache.org/jira/browse/CASSANDRA-9191 Project: Cassandra Issue Type: Bug Components: Core Reporter: Matt Stump Cassandra should have a way to log failed requests due to failure to obtain requested consistency. This should be logged as error or warning by default. Also exposed should be a counter for the benefit of opscenter. Currently the only way to log this is at the client. Often the application and DB teams are separate and it's very difficult to obtain client logs. Also because it's only visible to the client no visibility is given to opscenter making it difficult for the field to track down or isolate systematic or node level errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CASSANDRA-9191) Log and count failure to obtain requested consistency
[ https://issues.apache.org/jira/browse/CASSANDRA-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14495136#comment-14495136 ] Ryan Svihla edited comment on CASSANDRA-9191 at 4/14/15 11:25 PM: -- JMX counter at least maybe (or is that what you mean by 'expose' ? was (Author: rssvihla): JMX counter maybe? Log and count failure to obtain requested consistency - Key: CASSANDRA-9191 URL: https://issues.apache.org/jira/browse/CASSANDRA-9191 Project: Cassandra Issue Type: Bug Components: Core Reporter: Matt Stump Cassandra should have a way to log failed requests due to failure to obtain requested consistency. This should be logged as error or warning by default. Also exposed should be a counter for the benefit of opscenter. Currently the only way to log this is at the client. Often the application and DB teams are separate and it's very difficult to obtain client logs. Also because it's only visible to the client no visibility is given to opscenter making it difficult for the field to track down or isolate systematic or node level errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
