Fixed: set --es.num-shards to 1. By default jaeger st this value to 5…

[Dogild]

…, this could create some issues since we have only one node of elasticseearch here

Signed-off-by: Alexandre Wilhelm [email protected]

[pavolloffay]

I think we should rather set the number of replicas greater than 1. We do the same for C*.

[Dogild]

Not sure if it works out of the box for elastic search though. It needs some test first

[pavolloffay]

@Dogild I have created #46 which deploys two instances. It seems that it works unless there is something not obvious.

[pavolloffay]

It seems that #46 does not work properly. Data are not propagated to all nodes. We will revert to one replica in #50.

@Dogild could you please provide some references why 5 shards can cause problem with one ES node?

cc @yurishkuro @black-adder @mh-park

[Dogild]

@pavolloffay we experienced missing data and lost of connectivity between es and the the query node

[pavolloffay]

From what I have been told single ES node can still use multiple shards, It can even be more performant if it has enough resources compared to single shard node.

[pavolloffay]

@Dogild thanks for the PR. I will close it for now, based on my research it's valid to use more than 1 shard on a single node ES. It can lead to a better performance.

Please open an issue if you run into any problems with this configuration.

[pavolloffay]

I think the issue is with replicas. Our template should use zero replicas.