How to deploy a distributed jaeger deployment?

[Pure White]

hi all,

    I found out that the bottleneck of jaeger is collector and query, are these two components stateless so i can deploy multi collectors and multi querys?

[Won Jun Jang]

Yes, the collector and query services are stateless so you can deploy multiple versions of them. You might have to redeploy your agents with the new "collectorHostPorts"

On Wed, Dec 27, 2017 at 7:35 AM, Pure White <daniel...@gmail.com> wrote:

hi all,

    I found out that the bottleneck of jaeger is collector and query, are these two components stateless so i can deploy multi collectors and multi querys?

--
You received this message because you are subscribed to the Google Groups "Jaeger Tracing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jaeger-tracing+unsubscribe@googlegroups.com.
To post to this group, send email to jaeger-tracing@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jaeger-tracing/72495fc6-b4d6-44ba-a333-eae3210001b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Juraci Paixão Kröhling]

You might want to check our Kubernetes/OpenShift "production"
templates. They demonstrate how to start only the individual
components, allowing for each component to be scaled individually.

https://github.com/jaegertracing/jaeger-kubernetes
https://github.com/jaegertracing/jaeger-openshift

- Juca.