We are running test with 200 clients and 2000 docs. Each client pulls the 200 docs and then pushes a conflicting change to every doc.
What happens to sync_gateway during this test is that _changes longpoll starts taking ages, like 10 minutes or so and effectively the whole test just gets stucks, because longpoll timeouts everytime and never gets any changes.
If we stop the test and then wait a very long time (like 2 hours), we start getting changes using cURL eventually. So it seems that some “housekeeping” is going on during the test and it saturates the whole thing?
Is this a known issue, that large amount of conflicts jams the SG?