Description
We've identified that with larger nodes and with lots of client connections we're sometimes eating quite a lot of ram per smart client connection. Current known workaround is to have smart clients randomize node from which vbucket map updates are streamed. But there's likely a lot we can do on server side to dramatically lower memory consumption of such streaming connections.
Attachments
For Gerrit Dashboard: MB-5623 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
20885,4 | MB-5623: hibernate processes serving streaming clients | master | ns_server | Status: MERGED | +2 | +1 |