Heya,
The last time we fixed something along these lines was in 2019:
https://github.com/apache/couchdb/pull/2195/files
Which predates 3.1.0:
https://blog.couchdb.org/2020/05/06/3-0-1-3-1-0/
Are you 100% sure about your version?
A quick look does not suggest we have introduced this pattern again
since.
But CouchDB should behave fine in your scenario.
Can you try and remsh into the node and see which erlang processes
are hogging the CPU?
Also we should move this to the bug tracker if you can reproduce this
on 3.3.2.
Best
Jan
—