Description
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).
Attachments
Issue Links
For Gerrit Dashboard: MB-48522 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
163602,2 | MB-48522 do not block user updates during the select | master | ns_server | Status: MERGED | +2 | +1 |
163603,2 | MB-48522 elmininate the backlog of memcached refreshes after the user creation | master | ns_server | Status: MERGED | +2 | +1 |
163622,3 | MB-48522 fix broken user storage syncronization | master | ns_server | Status: MERGED | +2 | +1 |
165955,1 | MB-48522 fix broken user storage syncronization | mad-hatter | ns_server | Status: ABANDONED | 0 | 0 |
165956,1 | MB-48522 do not block user updates during the select | mad-hatter | ns_server | Status: ABANDONED | 0 | 0 |
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 |