cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10392) Allow Cassandra to trace to custom tracing implementations
Date Mon, 22 Feb 2016 21:34:18 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157729#comment-15157729
] 

T Jake Luciani commented on CASSANDRA-10392:
--------------------------------------------

I ran the utests and dtests against cassci

[trunk unittests|http://cassci.datastax.com/view/Dev/view/tjake/job/tjake-10392-tracing-testall/2/]
[trunk dtests|http://cassci.datastax.com/view/Dev/view/tjake/job/tjake-10392-tracing-dtest/lastCompletedBuild/testReport/]

There is one related failing dtest the materialized view one.

{code}
CassandraDaemon.java:195 - Exception in thread Thread[MessagingService-Incoming-/127.0.0.2,5,main]\njava.lang.AssertionError:
null\n\tat org.apache.cassandra.tracing.TraceState.<init>(TraceState.java:68) ~[main/:na]\n\tat
org.apache.cassandra.tracing.ExpiredTraceState.<init>(ExpiredTraceState.java:30) ~[main/:na]\n\tat
org.apache.cassandra.tracing.Tracing.initializeFromMessage(Tracing.java:244) ~[main/:na]\n\tat
org.apache.cassandra.net.MessagingService.receive(MessagingService.java:815) ~[main/:na]\n\tat
org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:198)
~[main/:na]\n\tat org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:178)
~[main/:na]\n\tat org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:92)
~[main/:na]']
{code}


> Allow Cassandra to trace to custom tracing implementations 
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-10392
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10392
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: mck
>            Assignee: mck
>             Fix For: 3.x
>
>         Attachments: 10392-trunk.txt, cassandra-dtest_master-10392.txt
>
>
> It can be possible to use an external tracing solution in Cassandra by abstracting out
the writing of tracing to system_traces tables in the tracing package to separate implementation
classes and leaving abstract classes in place that define the interface and behaviour otherwise
of C* tracing.
> Then via a system property "cassandra.custom_tracing_class" the Tracing class implementation
could be swapped out with something third party.
> An example of this is adding Zipkin tracing into Cassandra in the Summit [presentation|http://thelastpickle.com/files/2015-09-24-using-zipkin-for-full-stack-tracing-including-cassandra/presentation/tlp-reveal.js/tlp-cassandra-zipkin.html].
Code for the implemented Zipkin plugin can be found at https://github.com/thelastpickle/cassandra-zipkin-tracing/
> In addition this patch passes the custom payload through into the tracing session allowing
a third party tracing solution like Zipkin to do full-stack tracing from clients through and
into Cassandra.



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

Mime
View raw message