Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Replication stuck in busy state with test_multiple_cbls_updates_concurrently_with_push

See original GitHub issue

Builds

.net 2.0.0-b0571, SG 2.0.0-812, CBS 5.5.0-1924

Test Ran

pytest -s --mode=di --server-version=5.5.0-1924 --sync-gateway-version=2.0.0-812 --liteserv-platform=net-msft --liteserv-host=192.168.33.21 --liteserv-port=55555  --xattrs testsuites/CBLTester/CBL_Functional_tests/test_no_conflicts_cbl.py --liteserv-version=2.0.0-b0571 -k test_multiple_cbls_updates_concurrently_with_push  --create-db-per-test test-db --skip-provisioning

Actual

The test times out waiting for replicator to go idle. Test output

....
Activity level: busy
Got response: 
Got response: "busy"
Activity level: busy
FAILED
.....
>       replicator2.wait_until_replicator_idle(repl)
.....
E           Failed: Timeout >900s

CBL logs

INFO) Sync {DBWorker#10} Saved local checkpoint cp-42vjx9lioMn1AspGRraDwa9UphU= to db
INFO) Sync (Replicator) [13] 2018-02-27T13:53:37.7792737-08:00 Replicator[<*> DB[C:\mobile-testkit\CBLClient\Apps\CBLTestServer-Dotnet\TestServer.NetCore\bin\Debug\netcoreapp2.0\CouchbaseLite\cbl_db21519768338.06.cblite2\]] is Busy, progress 840570/859654
INFO) Sync (Replicator) [12] 2018-02-27T13:53:37.7870335-08:00 Replicator[<*> DB[C:\mobile-testkit\CBLClient\Apps\CBLTestServer-Dotnet\TestServer.NetCore\bin\Debug\netcoreapp2.0\CouchbaseLite\cbl_db21519768338.06.cblite2\]] is Busy, progress 840570/859654

The replicator is stuck in busy state and there is no activity.