You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2019/09/23 14:59:10 UTC

[GitHub] [skywalking] yangyshdan commented on issue #2653: Improve Zipkin<->SkyWalking integration

yangyshdan commented on issue #2653: Improve Zipkin<->SkyWalking integration
URL: https://github.com/apache/skywalking/issues/2653#issuecomment-534138020
 
 
   Hi, I just came across this interesting issue, because we are hitting this problem when we are evaluating Skywalking for our production environment for the zipkin client.  
   
   I think the core problem is that, in the distributed OLA envirnoment, one single OLA needs to collect all the span information in order to calculate the segment informatoin. I have a draft work-around idea, and would like to discuss here. 
   
   Lets say, we put a Kafka broker in the middle of zipkin and skywalking OLA, and all span informaiton with the same traceid is routed to the same partitoin of the Kafka topic, and all the messages of one particular partition will be delivered to the same OLA node. Will this solution solve the problem in certain degree?  Dear @wu-sheng, looking forward for your response. Thanks.

----------------------------------------------------------------
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