You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The riak_kv code has multiple capability checks (cluster-wide checks that all nodes support the capability) for capabilities that have existed since Riak 2.0 or before.
Capability checks are cheap, but not free. There are two capability checks in every encode_item call for handoff - so they may be called 1000s of times per second.
There has been anecdotal evidence of situations where during node failure events capability checks have reverted back to old capabilities - and then caused unexpected behaviour - in particular with the object_format capability check.
For 3.4 - we should sweep through these old capability checks and remove, default to the expected capability.
The text was updated successfully, but these errors were encountered:
martinsumner
changed the title
Capability checks for very old capabilites
Capability checks for very old capabilities
Jan 10, 2025
The
riak_kv
code has multiple capability checks (cluster-wide checks that all nodes support the capability) for capabilities that have existed since Riak 2.0 or before.Capability checks are cheap, but not free. There are two capability checks in every encode_item call for handoff - so they may be called 1000s of times per second.
There has been anecdotal evidence of situations where during node failure events capability checks have reverted back to old capabilities - and then caused unexpected behaviour - in particular with the object_format capability check.
For 3.4 - we should sweep through these old capability checks and remove, default to the expected capability.
The text was updated successfully, but these errors were encountered: