Nick Vatamaniuc

For the failing tests we'd probably want to either mock config get or make sure config app is started.

These conflicts shards typically are benign. They result from concurrent updates to `_dbs`. When the same database gets created concurrently and they maybe some network or temporary partition delay. After...

(sorry closed by accident)

Wonder if this is still an issue. We recently in 3.3.0 updated the collation driver. Would you mind giving 3.3.3 a try?

* If you don't see the replications in `_scheduler/jobs` try passing in a higher `limit=N` value. By default `_scheduler/jobs` returns the first 100 jobs if you have more, pass in...

Do the source servers show any errors in the logs ` failed due to error {connection_closed,mid_stream}` indicates something interrupted the changes feeds while it was reading or waiting on data....

Thanks for trying the settings out. > The replica access master using load balancer , the timeout in load balancer is 2 min (120 sec), we see replication crashes after...

``` state: {os_proc,"./bin/couchjs ./share/server/main.js",#Port, [error] 2023-11-30T07:45:35.406044Z couchdb@localhost -------- OS Process died with status: 143 [error] 2023-11-30T07:45:35.406269Z couchdb@localhost -------- gen_server terminated with reason: {exit_status,143} ``` This indicates `couch_js` processes are being...

Sorry, we had completely missed this issue somehow. @CoHageluken do you happen to have any logs from the replication jobs. They might indicate why the replication is stalling. Also try...

Another one. This one doesn't explicitly show a couch_js execution error but it failed to build an index: ``` [2023-12-13T04:34:11.011Z] module 'couch_mrview_ddoc_updated_tests' [2023-12-13T04:34:11.011Z] Check ddoc update actions [2023-12-13T04:34:11.011Z] undefined [2023-12-13T04:34:11.011Z]...