In order to investigate issue faced when adding 10 nodes to the prod cluster we will create a new cluster connected to the prod and will try reproduce the issue running multiple queries on it
TODO:
- Update grafana dashboard GC
- Reset config to rely on default one with only the udp_preference_limit setting and ensure still work
- Discuss with kdc managing team (for network looking at the low number of loss not sure they can help)
- See if there are some other kerberos config that can be tuned (knowing we rely on java)
- re-enable service check on puppet and presto once added back to prod cluster
- add metrics on jmx exporter (splits state, thread usage of different pool) -> PR
- revert to default config only add join-distribution-type=AUTOMATIC -> PR
- remove verbose GC tags: -XX:+PrintGCApplicationConcurrentTime
- enable tcp first on kdc query
- write doc with java thread analysis -> https://wikitech.wikimedia.org/wiki/Data_Engineering/Systems/Java







