zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andor Molnar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2990) Implement probabilistic tracing
Date Wed, 05 Sep 2018 10:17:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604232#comment-16604232

Andor Molnar commented on ZOOKEEPER-2990:


What are the target versions of this patch?

I suggest 3.5 and 3.6 only, because it's a minor improvement. (should only fix critical and
security issues in 3.4)

> Implement probabilistic tracing
> -------------------------------
>                 Key: ZOOKEEPER-2990
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2990
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Bogdan Kanivets
>            Assignee: Bogdan Kanivets
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
> It would be nice to have an ability to do probabilistic tracing similar to Cassandra 
> This will help debug issues in prod systems.
> I'd like to contribute if everyone is ok with the feature.
> My suggestion is to add an extra parameter to ZooTrace to handle it. Questions:
>  * should it be one global param or per each ZooTrace mask? I'm thinking per mask
>  * should it be a new 4lw or part of 'stmk'? Leaning towards new word and refactoring
param passing to words (stmk is a special case right now).
>  * there are places in the code that use LOG.trace directly. That will have to change
to ZooTrace
> I can make some initial implementation for demo/review.

This message was sent by Atlassian JIRA

View raw message