Made it possible to pass in the app name into register and avoid the module/pid application lookup.
…turning false for an unknown arch.
Only consumer I could find was in riak_kv_vnode - and that was wrapping vclock:get_counter with a function to do the conversion.
Membership is no longer derived from ownership.
Tickets: AZ462 AZ533 AZ630 AZ642 Fixes: BZ1024 BZ878 BZ688 BZ931 BZ869 Change cluster membership/gossip/ring in the following manner: -- Partition ownership and cluster membership are decoupled concepts. -- A single node in the cluster makes all partition claim decisions in a deterministic manner, avoiding endless churn possible in random merging. This single node (the claimant) can be assumed by any node in the cluster, and therefore avoids introducing a single point of failure. -- All data from all vnode modules is guaranteed to be handed off to a new owner before the owner takes over ownership for a partition, thus avoiding requests prematurely being sent to a node that does not yet have the data. -- Nodes will always handoff their data before cleaning exiting the cluster, even if the node is restarted before finishing handoff. -- Waiting for ring convergence is now part of the gossip/membership protocol, and is used to ensure consistent ring transitions across the cluster. -- Joining/leaving a cluster is handled more gracefully, and there is no need to wait for ring convergence (riak-admin ring-ready) as is previously suggested. Adding 20 nodes to a cluster at once should "just work". -- Handoff related to partition ownership changes can now occur under load, therefore allowing a cluster to scale up/down while handling normal requests. Other changes: -- Support for new commands: member_status, ring_status. -- Tracking of various new riak_core stats.
Saves re-createing tuples.
Runtimes got very long around the 64k case.
…om bucket before doing the fixup az616