[TEST] Disconnect from newly added nodes if cluster state publishing fails

Companion commit for elastic/elasticsearchelastic/elasticsearch#21197

Original commit: elastic/x-pack-elasticsearch@248a6bfb7c
This commit is contained in:
Yannick Welsch 2016-10-31 15:36:54 +01:00
parent f696ad1d10
commit 8350a8b2d8
1 changed files with 3 additions and 2 deletions

View File

@ -43,6 +43,7 @@ import java.io.IOException;
import java.util.Collection; import java.util.Collection;
import java.util.Collections; import java.util.Collections;
import java.util.HashSet; import java.util.HashSet;
import java.util.List;
import java.util.Set; import java.util.Set;
import java.util.concurrent.CountDownLatch; import java.util.concurrent.CountDownLatch;
import java.util.concurrent.ExecutionException; import java.util.concurrent.ExecutionException;
@ -99,12 +100,12 @@ public class TransportMonitoringBulkActionTests extends ESTestCase {
Version.CURRENT)); Version.CURRENT));
clusterService.setNodeConnectionsService(new NodeConnectionsService(Settings.EMPTY, null, null) { clusterService.setNodeConnectionsService(new NodeConnectionsService(Settings.EMPTY, null, null) {
@Override @Override
public void connectToAddedNodes(ClusterChangedEvent event) { public void connectToNodes(List<DiscoveryNode> addedNodes) {
// skip // skip
} }
@Override @Override
public void disconnectFromRemovedNodes(ClusterChangedEvent event) { public void disconnectFromNodes(List<DiscoveryNode> removedNodes) {
// skip // skip
} }
}); });