Reenable accounting circuit breaker (#44495)
We have a new Lucene 8.2 snapshot on master and 7.x; hence we can re-enable the accounting on these branches. Relates #30290
This commit is contained in:
parent
34c6067018
commit
458f24c46a
|
@ -5708,7 +5708,6 @@ public class InternalEngineTests extends EngineTestCase {
|
|||
assertMaxSeqNoInCommitUserData(engine);
|
||||
}
|
||||
|
||||
@AwaitsFix(bugUrl = "https://issues.apache.org/jira/browse/LUCENE-8809")
|
||||
public void testRefreshAndFailEngineConcurrently() throws Exception {
|
||||
AtomicBoolean stopped = new AtomicBoolean();
|
||||
Semaphore indexedDocs = new Semaphore(0);
|
||||
|
|
|
@ -2426,16 +2426,15 @@ public final class InternalTestCluster extends TestCluster {
|
|||
CircuitBreaker fdBreaker = breakerService.getBreaker(CircuitBreaker.FIELDDATA);
|
||||
assertThat("Fielddata breaker not reset to 0 on node: " + name, fdBreaker.getUsed(), equalTo(0L));
|
||||
|
||||
// Mute this assertion until we have a new Lucene snapshot with https://issues.apache.org/jira/browse/LUCENE-8809.
|
||||
// try {
|
||||
// assertBusy(() -> {
|
||||
// CircuitBreaker acctBreaker = breakerService.getBreaker(CircuitBreaker.ACCOUNTING);
|
||||
// assertThat("Accounting breaker not reset to 0 on node: " + name + ", are there still Lucene indices around?",
|
||||
// acctBreaker.getUsed(), equalTo(0L));
|
||||
// });
|
||||
// } catch (Exception e) {
|
||||
// throw new AssertionError("Exception during check for accounting breaker reset to 0", e);
|
||||
// }
|
||||
try {
|
||||
assertBusy(() -> {
|
||||
CircuitBreaker acctBreaker = breakerService.getBreaker(CircuitBreaker.ACCOUNTING);
|
||||
assertThat("Accounting breaker not reset to 0 on node: " + name + ", are there still Lucene indices around?",
|
||||
acctBreaker.getUsed(), equalTo(0L));
|
||||
});
|
||||
} catch (Exception e) {
|
||||
throw new AssertionError("Exception during check for accounting breaker reset to 0", e);
|
||||
}
|
||||
|
||||
// Anything that uses transport or HTTP can increase the
|
||||
// request breaker (because they use bigarrays), because of
|
||||
|
|
Loading…
Reference in New Issue