Enable trace logging in CCR retention lease tests

These tests are failing somewhat mysteriously, indicating that when we
renew retention leaess during a restore that our retention leases that
we added before starting the restore suddenly do not exist. To make
sense of this, this commit enables trace logging.
This commit is contained in:
Jason Tedor 2019-05-07 22:44:47 -04:00
parent d5b0badeb7
commit 8bea3c3a58
No known key found for this signature in database
GPG Key ID: FA89F05560F16BC5

View File

@ -44,6 +44,7 @@ import org.elasticsearch.indices.IndicesService;
import org.elasticsearch.plugins.Plugin;
import org.elasticsearch.snapshots.RestoreInfo;
import org.elasticsearch.snapshots.RestoreService;
import org.elasticsearch.test.junit.annotations.TestLogging;
import org.elasticsearch.test.transport.MockTransportService;
import org.elasticsearch.transport.ConnectTransportException;
import org.elasticsearch.transport.RemoteTransportException;
@ -87,6 +88,7 @@ import static org.hamcrest.Matchers.equalTo;
import static org.hamcrest.Matchers.greaterThan;
import static org.hamcrest.Matchers.hasSize;
@TestLogging(value = "org.elasticsearch.xpack.ccr:trace")
public class CcrRetentionLeaseIT extends CcrIntegTestCase {
public static final class RetentionLeaseRenewIntervalSettingPlugin extends Plugin {
@ -614,7 +616,6 @@ public class CcrRetentionLeaseIT extends CcrIntegTestCase {
});
}
@AwaitsFix(bugUrl = "https://github.com/elastic/elasticsearch/issues/39509")
public void testRetentionLeaseRenewalIsCancelledWhenFollowingIsPaused() throws Exception {
final String leaderIndex = "leader";
final String followerIndex = "follower";
@ -921,7 +922,6 @@ public class CcrRetentionLeaseIT extends CcrIntegTestCase {
}
}
@AwaitsFix( bugUrl = "https://github.com/elastic/elasticsearch/issues/39850")
public void testForgetFollower() throws Exception {
final String leaderIndex = "leader";
final String followerIndex = "follower";