You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@zookeeper.apache.org by GitBox <gi...@apache.org> on 2019/11/15 18:51:02 UTC

[GitHub] [zookeeper] lvfangmin commented on issue #994: ZOOKEEPER-3432 Improving zookeeper trace for performance and scalability

lvfangmin commented on issue #994: ZOOKEEPER-3432 Improving zookeeper trace for performance and scalability
URL: https://github.com/apache/zookeeper/pull/994#issuecomment-554483160
 
 
   @maoling it makes sense to leave the possibility of integrating with 3rd party like openTracing, but it seems to me we can do that in a separate JIRA.
   
   Most of the code here are focusing on where we collect and generate the trace event, it's not that much about how to send the tracing, we can adapt that to the openTracing later.
   
   Given we've already running this on prod for a long time, I would suggest to keep minimal change on this for now and improve it separately, what's your idea?
   
   @gmcatsf can you rebase this feature and keep this up to date?
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services