Description
We currently are in a situation where we would like to use a different string than the key for hashing and selection of the destination vBucket. This can be useful to keep all of a single user data on many keys but on the same vBucket (and therefore servers), and allow for node downtime to only affect a percentage of the user base instead of the full user base. More generally, it could be used to gain better control over the distribution of data over the nodes.
Looking at the current code, I guess it would be safer not to touch the hashing but just allow for the hashing of a separate string?
Attachments
For Gerrit Dashboard: CCBC-119 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
22395,2 | CCBC-119: Allow the user to specify a different hash key | master | libcouchbase | Status: MERGED | +2 | +1 |