Keep nodes above watermark in testAutomaticReleaseOfIndexBlock (#47387)
Today the comment boldly claims that this line of code keeps nodes above the 10-byte low watermark when in fact this is not true at all. This change fixes this so that it really does keep nodes above the low watermark. Fixes #45338. Again.
This commit is contained in:
parent
0179f93544
commit
99b25d3740
|
@ -185,7 +185,7 @@ public class MockDiskUsagesIT extends ESIntegTestCase {
|
||||||
// Move all nodes above the low watermark so no shard movement can occur, and at least one node above the flood stage watermark so
|
// Move all nodes above the low watermark so no shard movement can occur, and at least one node above the flood stage watermark so
|
||||||
// the index is blocked
|
// the index is blocked
|
||||||
clusterInfoService.diskUsageFunction = (discoveryNode, fsInfoPath) -> setDiskUsage(fsInfoPath, 100,
|
clusterInfoService.diskUsageFunction = (discoveryNode, fsInfoPath) -> setDiskUsage(fsInfoPath, 100,
|
||||||
discoveryNode.getId().equals(nodeIds.get(2)) ? between(0, 4) : between(0, 14));
|
discoveryNode.getId().equals(nodeIds.get(2)) ? between(0, 4) : between(0, 9));
|
||||||
|
|
||||||
assertBusy(() -> assertBlocked(
|
assertBusy(() -> assertBlocked(
|
||||||
client().prepareIndex().setIndex("test").setType("doc").setId("1").setSource("foo", "bar"),
|
client().prepareIndex().setIndex("test").setType("doc").setId("1").setSource("foo", "bar"),
|
||||||
|
|
Loading…
Reference in New Issue