neon
neon copied to clipboard
neondatabase
Test test_backpressure_received_lsn_lag does not pass when failpoint is properly enabled
In https://github.com/neondatabase/neon/pull/1571 I discovered that failpoints were not enabled, and after fixing failpoint integration test_backpressure_received_lsn_lag started to fail. Currently, it fails because it reaches statement_timeout. I tried to increase it up to 10 minutes but it didnt help. Needs more investigation. @lubennikovaav could you please take a look?
this test confims that backpressure works backpressure ensures that when compute has a very intensive write workload, we don't time out on reads
Merging #596 into this one.
Cross posting the idea:
Lets also test backpressure via applying CPU limits on pageserver
What that should prove? If the pageserver is slow enough then back pressure kicks in and slows down the compute. What is the goal or suspected misbehavior?
Not sure I follow the last question.
If the pageserver is slow enough then back pressure kicks in and slows down the compute.
Yes, we need to prove that it works as intended.
Yes, we need to prove that it works as intended.
Sure, what would be the proof or the test to validate that? My point is that if due to the failpoints (aka slow pageserver) compute times out that means that back pressure works as expected.