25d60e152f
The tribe node creates one local client node for each cluster it connects to. Refactorings in #13383 broke this so that each local client node now tries to load the full elasticsearch.yml that the real tribe node uses. This change fixes the problem by adding a TribeClientNode which is a subclass of Node. The Environment the node uses is now passed in (in place of Settings), and the TribeClientNode simply does not use InternalSettingsPreparer.prepareEnvironment. The tests around tribe nodes are not great. The existing tests pass, but I also manually tested by creating 2 local clusters, and configuring and starting a tribe node. With this I was able to see in the logs the tribe node connecting to each cluster. closes #13383 |
||
|---|---|---|
| .. | ||
| evil-tests | ||
| smoke-test-client | ||
| smoke-test-multinode | ||
| smoke-test-plugins | ||
| vagrant | ||