enable debug logging for testMasterFailoverDuringIndexingWithMappingChanges
This commit is contained in:
parent
4c28e781dd
commit
7291aba8ae
|
@ -31,6 +31,7 @@ import org.elasticsearch.test.discovery.TestZenDiscovery;
|
||||||
import org.elasticsearch.test.disruption.NetworkDisruption;
|
import org.elasticsearch.test.disruption.NetworkDisruption;
|
||||||
import org.elasticsearch.test.disruption.NetworkDisruption.NetworkDisconnect;
|
import org.elasticsearch.test.disruption.NetworkDisruption.NetworkDisconnect;
|
||||||
import org.elasticsearch.test.disruption.NetworkDisruption.TwoPartitions;
|
import org.elasticsearch.test.disruption.NetworkDisruption.TwoPartitions;
|
||||||
|
import org.elasticsearch.test.junit.annotations.TestLogging;
|
||||||
import org.elasticsearch.test.transport.MockTransportService;
|
import org.elasticsearch.test.transport.MockTransportService;
|
||||||
|
|
||||||
import java.util.Arrays;
|
import java.util.Arrays;
|
||||||
|
@ -64,6 +65,7 @@ public class IndexingMasterFailoverIT extends ESIntegTestCase {
|
||||||
* If the master node is being disrupted or if it cannot commit cluster state changes, it needs to retry within timeout limits.
|
* If the master node is being disrupted or if it cannot commit cluster state changes, it needs to retry within timeout limits.
|
||||||
* This retry logic is implemented in TransportMasterNodeAction and tested by the following master failover scenario.
|
* This retry logic is implemented in TransportMasterNodeAction and tested by the following master failover scenario.
|
||||||
*/
|
*/
|
||||||
|
@TestLogging("_root:DEBUG")
|
||||||
public void testMasterFailoverDuringIndexingWithMappingChanges() throws Throwable {
|
public void testMasterFailoverDuringIndexingWithMappingChanges() throws Throwable {
|
||||||
logger.info("--> start 4 nodes, 3 master, 1 data");
|
logger.info("--> start 4 nodes, 3 master, 1 data");
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue