zipkin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator-zipkin] adriancole commented on issue #1778: Zipkin host collector (agent)
Date Fri, 10 May 2019 00:47:32 GMT
adriancole commented on issue #1778: Zipkin host collector (agent)
URL: https://github.com/apache/incubator-zipkin/issues/1778#issuecomment-491115281
 
 
   I think this issue is pie in the sky and also wouldn't affect the codebase in this repo.
   
   I think people close to the codebase here will know there's extensive work vs ticking boxes,
for example how and which logs are written, metrics are emitted, what can be supported or
extended, how many people can and how close are they to the project. I won't troll by citing
numerous examples of projects either not prioritizing things like format parity, data size,
or abandonment. Suffice to say either a 3rd party or 1st party clone isn't going to replace
this server. If someone wants to (as they always could have), they can write a contrib proxy,
make it popular etc, or help other proxies like pitchfork or census.
   
   Meanwhile, we undersell largely our own server. While we are focused on a lot of things,
we've updated this to literally use the same infra as those who left twitter with the experience
of the first attempt (finagle -> armeria). We also have numerous works in progress to reduce
memory overhead per request and also address things like rate limiting. Duplicating all of
this in a new language for the sake of it is expensive. Again folks can, but personally I
see no advantage intentionally not improving our server, especially after all the investments
we've made.
   
   So, basically I agree with @devinsba and @anuraaga .. if there's concrete concern about
which JVM should be used, we can address that in docker image. If there are overhead improvements,
nothing to stop them happening here. If someone wants to experiment with another agent, there
are places to do that including 3rd party repos, personal repos and contrib.
   
   Meanwhile, this repo is in a different org now, apache. If we did anything else, that would
either not be in this org, or a new incubator entry. Suffice to say this issue is out-of-date,
even if insightful, so closing.
   
   Thanks to all for the feedback!

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

Mime
View raw message