[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2019-06-13 Thread Jeremy Hanna (JIRA)


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

Jeremy Hanna updated CASSANDRA-5992:

Complexity: Low Hanging Fruit

> Add a logger.trace call to Tracing
> --
>
> Key: CASSANDRA-5992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Observability
>Reporter: Jeremiah Jordan
>Assignee: Ryan Magnusson
>Priority: Low
>  Labels: lhf
> Fix For: 4.x
>
> Attachments: CASSANDRA-5992.txt
>
>
> A bunch of stuff is now written to Tracing, and there are no logging trace 
> calls any more.  If a node is having issues on the read/write path and 
> tracing can't actually save data, there is no way to see through logging what 
> is going on.  Would be nice if we made all Tracing messages also go out at 
> logger.trace so that you could enable that to debug stuff.
> Being able to change the RF of the system_traces KS might also help here, but 
> there would still be classes of problems that it would be good to have the 
> logging there for. Added CASSANDRA-6016 for that.



--
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-5992) Add a logger.trace call to Tracing

2018-11-18 Thread C. Scott Andreas (JIRA)


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

C. Scott Andreas updated CASSANDRA-5992:

Component/s: Observability

> Add a logger.trace call to Tracing
> --
>
> Key: CASSANDRA-5992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Observability
>Reporter: Jeremiah Jordan
>Assignee: Ryan Magnusson
>Priority: Minor
>  Labels: lhf
> Fix For: 4.x
>
> Attachments: CASSANDRA-5992.txt
>
>
> A bunch of stuff is now written to Tracing, and there are no logging trace 
> calls any more.  If a node is having issues on the read/write path and 
> tracing can't actually save data, there is no way to see through logging what 
> is going on.  Would be nice if we made all Tracing messages also go out at 
> logger.trace so that you could enable that to debug stuff.
> Being able to change the RF of the system_traces KS might also help here, but 
> there would still be classes of problems that it would be good to have the 
> logging there for. Added CASSANDRA-6016 for that.



--
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-5992) Add a logger.trace call to Tracing

2016-06-30 Thread Marcus Eriksson (JIRA)

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

Marcus Eriksson updated CASSANDRA-5992:
---
Assignee: Ryan Magnusson
  Status: Open  (was: Patch Available)

cancelling patch until it has been rebased

> Add a logger.trace call to Tracing
> --
>
> Key: CASSANDRA-5992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Jeremiah Jordan
>Assignee: Ryan Magnusson
>Priority: Minor
>  Labels: lhf
> Fix For: 3.x
>
> Attachments: CASSANDRA-5992.txt
>
>
> A bunch of stuff is now written to Tracing, and there are no logging trace 
> calls any more.  If a node is having issues on the read/write path and 
> tracing can't actually save data, there is no way to see through logging what 
> is going on.  Would be nice if we made all Tracing messages also go out at 
> logger.trace so that you could enable that to debug stuff.
> Being able to change the RF of the system_traces KS might also help here, but 
> there would still be classes of problems that it would be good to have the 
> logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2016-04-07 Thread Marcus Eriksson (JIRA)

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

Marcus Eriksson updated CASSANDRA-5992:
---
Fix Version/s: 3.x

> Add a logger.trace call to Tracing
> --
>
> Key: CASSANDRA-5992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Jeremiah Jordan
>Priority: Minor
>  Labels: lhf
> Fix For: 3.x
>
> Attachments: CASSANDRA-5992.txt
>
>
> A bunch of stuff is now written to Tracing, and there are no logging trace 
> calls any more.  If a node is having issues on the read/write path and 
> tracing can't actually save data, there is no way to see through logging what 
> is going on.  Would be nice if we made all Tracing messages also go out at 
> logger.trace so that you could enable that to debug stuff.
> Being able to change the RF of the system_traces KS might also help here, but 
> there would still be classes of problems that it would be good to have the 
> logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2016-04-06 Thread Marcus Eriksson (JIRA)

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

Marcus Eriksson updated CASSANDRA-5992:
---
Reviewer: Marcus Eriksson

> Add a logger.trace call to Tracing
> --
>
> Key: CASSANDRA-5992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Jeremiah Jordan
>Priority: Minor
>  Labels: lhf
> Attachments: CASSANDRA-5992.txt
>
>
> A bunch of stuff is now written to Tracing, and there are no logging trace 
> calls any more.  If a node is having issues on the read/write path and 
> tracing can't actually save data, there is no way to see through logging what 
> is going on.  Would be nice if we made all Tracing messages also go out at 
> logger.trace so that you could enable that to debug stuff.
> Being able to change the RF of the system_traces KS might also help here, but 
> there would still be classes of problems that it would be good to have the 
> logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2016-04-04 Thread Jeremiah Jordan (JIRA)

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

Jeremiah Jordan updated CASSANDRA-5992:
---
Status: Patch Available  (was: Reopened)

> Add a logger.trace call to Tracing
> --
>
> Key: CASSANDRA-5992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Jeremiah Jordan
>Priority: Minor
>  Labels: lhf
> Attachments: CASSANDRA-5992.txt
>
>
> A bunch of stuff is now written to Tracing, and there are no logging trace 
> calls any more.  If a node is having issues on the read/write path and 
> tracing can't actually save data, there is no way to see through logging what 
> is going on.  Would be nice if we made all Tracing messages also go out at 
> logger.trace so that you could enable that to debug stuff.
> Being able to change the RF of the system_traces KS might also help here, but 
> there would still be classes of problems that it would be good to have the 
> logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2015-09-16 Thread Aleksey Yeschenko (JIRA)

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

Aleksey Yeschenko updated CASSANDRA-5992:
-
Fix Version/s: (was: 2.0.x)

> Add a logger.trace call to Tracing
> --
>
> Key: CASSANDRA-5992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Core
>Reporter: Jeremiah Jordan
>Priority: Minor
>  Labels: lhf
> Attachments: CASSANDRA-5992.txt
>
>
> A bunch of stuff is now written to Tracing, and there are no logging trace 
> calls any more.  If a node is having issues on the read/write path and 
> tracing can't actually save data, there is no way to see through logging what 
> is going on.  Would be nice if we made all Tracing messages also go out at 
> logger.trace so that you could enable that to debug stuff.
> Being able to change the RF of the system_traces KS might also help here, but 
> there would still be classes of problems that it would be good to have the 
> logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2015-08-07 Thread Ryan Magnusson (JIRA)

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

Ryan Magnusson updated CASSANDRA-5992:
--
Attachment: CASSANDRA-5992.txt

add logger.trace whenever Tracing.trace is called.

 Add a logger.trace call to Tracing
 --

 Key: CASSANDRA-5992
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Jeremiah Jordan
Priority: Minor
  Labels: lhf
 Fix For: 2.0.x

 Attachments: CASSANDRA-5992.txt


 A bunch of stuff is now written to Tracing, and there are no logging trace 
 calls any more.  If a node is having issues on the read/write path and 
 tracing can't actually save data, there is no way to see through logging what 
 is going on.  Would be nice if we made all Tracing messages also go out at 
 logger.trace so that you could enable that to debug stuff.
 Being able to change the RF of the system_traces KS might also help here, but 
 there would still be classes of problems that it would be good to have the 
 logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2015-03-18 Thread Philip Thompson (JIRA)

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

Philip Thompson updated CASSANDRA-5992:
---
Labels: lhf  (was: )
Issue Type: Improvement  (was: Bug)

 Add a logger.trace call to Tracing
 --

 Key: CASSANDRA-5992
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Jeremiah Jordan
Priority: Minor
  Labels: lhf
 Fix For: 2.0.14


 A bunch of stuff is now written to Tracing, and there are no logging trace 
 calls any more.  If a node is having issues on the read/write path and 
 tracing can't actually save data, there is no way to see through logging what 
 is going on.  Would be nice if we made all Tracing messages also go out at 
 logger.trace so that you could enable that to debug stuff.
 Being able to change the RF of the system_traces KS might also help here, but 
 there would still be classes of problems that it would be good to have the 
 logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2015-01-20 Thread T Jake Luciani (JIRA)

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

T Jake Luciani updated CASSANDRA-5992:
--
Fix Version/s: (was: 2.0.12)
   2.0.13

 Add a logger.trace call to Tracing
 --

 Key: CASSANDRA-5992
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Jeremiah Jordan
Priority: Minor
 Fix For: 2.0.13


 A bunch of stuff is now written to Tracing, and there are no logging trace 
 calls any more.  If a node is having issues on the read/write path and 
 tracing can't actually save data, there is no way to see through logging what 
 is going on.  Would be nice if we made all Tracing messages also go out at 
 logger.trace so that you could enable that to debug stuff.
 Being able to change the RF of the system_traces KS might also help here, but 
 there would still be classes of problems that it would be good to have the 
 logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2014-07-30 Thread Michael Shuler (JIRA)

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

Michael Shuler updated CASSANDRA-5992:
--

Fix Version/s: (was: 1.2.19)

 Add a logger.trace call to Tracing
 --

 Key: CASSANDRA-5992
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Jeremiah Jordan
Priority: Minor
 Fix For: 2.0.10, 2.1.1


 A bunch of stuff is now written to Tracing, and there are no logging trace 
 calls any more.  If a node is having issues on the read/write path and 
 tracing can't actually save data, there is no way to see through logging what 
 is going on.  Would be nice if we made all Tracing messages also go out at 
 logger.trace so that you could enable that to debug stuff.
 Being able to change the RF of the system_traces KS might also help here, but 
 there would still be classes of problems that it would be good to have the 
 logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2014-07-29 Thread Michael Shuler (JIRA)

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

Michael Shuler updated CASSANDRA-5992:
--

Fix Version/s: 2.1.1
   2.0.10

 Add a logger.trace call to Tracing
 --

 Key: CASSANDRA-5992
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Jeremiah Jordan
Priority: Minor
 Fix For: 1.2.19, 2.0.10, 2.1.1


 A bunch of stuff is now written to Tracing, and there are no logging trace 
 calls any more.  If a node is having issues on the read/write path and 
 tracing can't actually save data, there is no way to see through logging what 
 is going on.  Would be nice if we made all Tracing messages also go out at 
 logger.trace so that you could enable that to debug stuff.
 Being able to change the RF of the system_traces KS might also help here, but 
 there would still be classes of problems that it would be good to have the 
 logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2014-07-29 Thread Michael Shuler (JIRA)

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

Michael Shuler updated CASSANDRA-5992:
--

Fix Version/s: 1.2.19

 Add a logger.trace call to Tracing
 --

 Key: CASSANDRA-5992
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Jeremiah Jordan
Priority: Minor
 Fix For: 1.2.19, 2.0.10, 2.1.1


 A bunch of stuff is now written to Tracing, and there are no logging trace 
 calls any more.  If a node is having issues on the read/write path and 
 tracing can't actually save data, there is no way to see through logging what 
 is going on.  Would be nice if we made all Tracing messages also go out at 
 logger.trace so that you could enable that to debug stuff.
 Being able to change the RF of the system_traces KS might also help here, but 
 there would still be classes of problems that it would be good to have the 
 logging there for. Added CASSANDRA-6016 for that.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (CASSANDRA-5992) Add a logger.trace call to Tracing

2013-09-12 Thread Jeremiah Jordan (JIRA)

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

Jeremiah Jordan updated CASSANDRA-5992:
---

Description: 
A bunch of stuff is now written to Tracing, and there are no logging trace 
calls any more.  If a node is having issues on the read/write path and tracing 
can't actually save data, there is no way to see through logging what is going 
on.  Would be nice if we made all Tracing messages also go out at logger.trace 
so that you could enable that to debug stuff.

Being able to change the RF of the system_traces KS might also help here, but 
there would still be classes of problems that it would be good to have the 
logging there for. Added CASSANDRA-6016 for that.

  was:
A bunch of stuff is now written to Tracing, and there are no logging trace 
calls any more.  If a node is having issues on the read/write path and tracing 
can't actually save data, there is no way to see through logging what is going 
on.  Would be nice if we made all Tracing messages also go out at logger.trace 
so that you could enable that to debug stuff.

Being able to change the RF of the system_traces KS might also help here, but 
there would still be classes of problems that it would be good to have the 
logging there for.


 Add a logger.trace call to Tracing
 --

 Key: CASSANDRA-5992
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5992
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Jeremiah Jordan
Priority: Minor

 A bunch of stuff is now written to Tracing, and there are no logging trace 
 calls any more.  If a node is having issues on the read/write path and 
 tracing can't actually save data, there is no way to see through logging what 
 is going on.  Would be nice if we made all Tracing messages also go out at 
 logger.trace so that you could enable that to debug stuff.
 Being able to change the RF of the system_traces KS might also help here, but 
 there would still be classes of problems that it would be good to have the 
 logging there for. Added CASSANDRA-6016 for that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira