MetricsIODispatcherTest.testPeerIsSlowToRead test

To reproduce

2024-03-20T15:41:12.6653541Z 2024-03-20T15:41:12.448659Z I i.q.c.p.WalWriterPool closed
2024-03-20T15:41:12.6654123Z Tests run: 10, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 64.895 sec <<< FAILURE! - in io.questdb.test.cutlass.http.MetricsIODispatcherTest
2024-03-20T15:41:12.6654576Z testPeerIsSlowToRead(io.questdb.test.cutlass.http.MetricsIODispatcherTest)  Time elapsed: 0.512 sec  <<< FAILURE!
2024-03-20T15:41:12.6654982Z java.lang.AssertionError: expected:<0> but was:<1>
2024-03-20T15:41:12.6655316Z 	at org.junit.Assert.fail(Assert.java:89)
2024-03-20T15:41:12.6655662Z 	at org.junit.Assert.failNotEquals(Assert.java:835)
2024-03-20T15:41:12.6656018Z 	at org.junit.Assert.assertEquals(Assert.java:647)
2024-03-20T15:41:12.6656376Z 	at org.junit.Assert.assertEquals(Assert.java:633)
2024-03-20T15:41:12.6656795Z 	at io.questdb.test.cutlass.http.MetricsIODispatcherTest.lambda$testPrometheusScenario$4(MetricsIODispatcherTest.java:263)
2024-03-20T15:41:12.6657306Z 	at io.questdb.test.cutlass.http.MetricsIODispatcherTest.lambda$buildClientCode$1(MetricsIODispatcherTest.java:187)

146.zip

QuestDB version:

7.3.10

OS, in case of Docker specify Docker and the Host OS:

linux

File System, in case of Docker specify Host File System:

ext4

Full Name:

Alex Pelagenko

Affiliation:

QuestDb

Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?

• Yes, I have

Additional context

No response

Start with io.questdb.test.cutlass.http.MetricsIODispatcherTest, especially testPeerIsSlowToRead and the assertions at lines 187 and 263. Run that test on Linux and compare the expected 0 versus actual 1 failure using the attached 146.zip context. Done means identifying the cause and making the test pass reliably.