As seen in a case in the field, customer need to create/delete large number of users in short succession. The customer is using secrete management solution (such as HashiCorp) in Kubernetes, where containers are created and destroyed in quick succession, and for each container, an ephemeral user is created and destroyed as well.
Current user CRUD API latency increases as number of users increases, due to the implementation nature of replication (replicated_dets).
|For Gerrit Dashboard: MB-49147|
|165965,2||MB-49147: Backport neo fixes for slow DETS||mad-hatter||ns_server||Status: ABANDONED||0||+1|
|165966,2||MB-49147: Backport neo fixes for slow DETS||mad-hatter||ns_server||Status: ABANDONED||0||+1|
|166188,4||MB-49147:[BP] Fixes for slow DETS||mad-hatter||ns_server||Status: MERGED||+2||+1|
|166794,2||Merge remote-tracking branch 'couchbase/mad-hatter'||master||ns_server||Status: MERGED||+2||+1|
|166854,1||Merge remote-tracking branch 'couchbase/mad-hatter'||cheshire-cat||ns_server||Status: MERGED||+2||+1|