Hello All,
Just in time for the weekend we bring you a rundown of... the mailing list!
As always, we want to hear from you. Let me know if you’re working on or
speaking about something Riak related and would like a shoutout. I’ll get
your talk, project or blog post in the next Riak Recap.
## Com
Hi Vladyslav,
If you recognize the full name of the object raising the sibling
warning, it is most likely a manifest object. Sometimes, during hinted
handoff, you can see these messages. They should resolve after handoff
completes.
Please see the documentation for the transfer-limit command as we
Hi Norman,
It's still the case. Riak KV was designed to be highly available, and
highly scalable key/value store with predictable low latency. This lets
you scale to a few or as many machines as needed, while removing any single
failure points that a single-machine database or cache might impose.
Hi.
I have a trouble with PUT to Riak CS cluster. During this process I
periodically see the following message in Riak error.log:
2016-06-03 11:15:55.201 [error]
<0.15536.142>@riak_kv_vnode:encode_and_put:2253 Put failure: too many
siblings for object OBJECT_NAME (101)
and also
2016-06-03 12:41
