Simon Willnauer 3d5f113ada

Ensure we don't use a remote profile if cluster name matches (#31331) ...

If we are running into a race condition between a node being configured
to be a remote node for cross cluster search etc. and that node joining
the cluster we might connect to that node with a remote profile. If that
node now joins the cluster it connected to it as a CCS remote node we use
the wrong profile and can't use bulk connections etc. anymore. This change
uses the remote profile only if we connect to a node that has a different cluster
name than the local cluster. This is not a perfect fix for this situation but
is the safe option while potentially only loose a small optimization of using
less connections per node which is small anyways since we only connect to a
small set of nodes.

Closes #29321

2018-06-17 13:32:53 +02:00

..

fixtures

[Tests] Mutualize fixtures code in BaseHttpFixture (#31210)

2018-06-14 14:09:56 +02:00

framework

Ensure we don't use a remote profile if cluster name matches (#31331)

2018-06-17 13:32:53 +02:00

logger-usage

Upgrade checkstyle to version 7.5

2017-02-03 09:46:44 -05:00

build.gradle

Build: Add 3rd party dependencies report generation (#27727)

2017-12-26 10:51:47 +01:00