Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: cet-bg-mgr-vno…
Commits on Dec 20, 2013
  1. Chris T
  2. Chris T
  3. Chris T

    Address remaining issues in PR

    buddhisthead authored
    * Remove lock defs file; it was moved to riak_kv_vnode.hrl since all these locks are KV-specific
    * The optional call to handoff_started/2 allows vnodes one last chance to abort the handoff process. the function is passed the source vnode's partition number and node name (this node) because the callback does not have access to the full vnode state at this time. In addition the worker pid is passed so the vnode may use that information in its decision to cancel the handoff or not (e.g. get a lock on behalf of the process)
    * Move code that calls handooff_started/2 into separate function and put the call inside the try/catch.
  4. Chris T

    Re-implement handoff integration.

    buddhisthead authored
    * rebase on latest background manager.
    * Add an optional callback entry point to the kv vnode: handoff_started/2
    * core_vnode will check for the optional function and call if present
    * returning max_concurrency will cause the handoff to be aborted and retried.
  5. Chris T

    Clean up query API

    buddhisthead authored
    * Remove history API, use unregistered to signal unavailability of bg-mgr, fix set_token_rate bug.
    * Prune the query API down to a consistent set of commands and adjust tests.
    * Change query API to use named ETS table directly; is not threaded through the gen_server.
  6. Chris T

    Concurrency API should return 'undefined' for limits when the ETS tab…

    buddhisthead authored
    …le is unavailable * Allows callers to try again later
  7. Chris T

    Add a background lock and task manager module to riak core.

    buddhisthead authored
    * The goal is to allow riak sub-systems to coordinate use of shared resources,
    * e.g. protect from concurrent vnode folds on the same partition.
    * Locks and tokens have a settable maximum concurrency limit.
    * "Taken" locks and tokens are tracked in an ETS table.
    * max_concurrency is returned when the set limits are reached.
    * Processes that take locks are monitored.
    * Locks are released when the taking processes terminate.
    * Tokens are refreshed at a specified periodic rate.
    * Token processes are not monitored because tokens never "release".
    * A table manager is introduced to add persistence across process crashes,
    * and to allow proper table transfer to occur without losing the table.
    * An EQC test exercises the majority of the API. see test/bg_manager_eqc.erl
    * See the original PR for background manager here: #364
Commits on Dec 19, 2013
  1. Jordan West

    Merge pull request #460 from basho/jrw-btype-prop-validation

    jrwest authored
    Validate Bucket Type Properties Required by Core
  2. Jordan West
  3. Jordan West

    added btypes_eqc to test bucket types creation invariants

    jrwest authored
    the test does not yet cover crashing and chaning the claimant or waiting for
    type properties to propogate to other nodes (for that we will probably need/use riak_test).
    However, it does reproduce #442
  4. Jordan West

    Merge pull request #457 from basho/jrw-cm-improvements

    jrwest authored
    Yet Another Round of Cluster Metadata Improvements (YAROCMI #1)
  5. Jordan West

    minor cleanup in riak_core_metadata & riak_core_broadcast

    jrwest authored
    * fix some whitespace
    * only allow valid boolean values for allow_put get option
Commits on Dec 12, 2013
  1. Christopher Meiklejohn

    Merge pull request #480 from basho/features/csm/connection-manager

    cmeiklejohn authored
    Port 1.4 changes to the 2.0 branch.
  2. Christopher Meiklejohn

    Remove ranch dependency.

    cmeiklejohn authored
  3. Christopher Meiklejohn

    Remove connection manager and service manager.

    cmeiklejohn authored
  4. Christopher Meiklejohn

    Extract riak_core_connection and tests.

    cmeiklejohn authored
  5. Christopher Meiklejohn

    Merge pull request #430 from basho/bugfix/csm/bad-type-specifications

    cmeiklejohn authored
    Fix bad type specifications.
  6. Scott Lystig Fritchie

    Merge pull request #421 from mbbx6spp/clean-up-.travis.yml

    slfritchie authored
    Update otp_release list in .travis.yml
Commits on Dec 11, 2013
  1. Joe DeVivo

    Merge pull request #478 from basho/jd-cuttlefish-api

    joedevivo authored
    New cuttlefish api functions
  2. New cuttlefish api functions

    Joe DeVivo authored
Commits on Dec 9, 2013
  1. Christopher Meiklejohn

    Merge pull request #471 from basho/feature/csm/sync-service-mgr-develop

    cmeiklejohn authored
    Provide a synchronous registration and unregistration of services.
  2. Christopher Meiklejohn

    Provide a synchronous registration and unregistration of services.

    cmeiklejohn authored
    Some parts of repl require being able to disable a service and block
    until it's disabled.  Provide this API.
Commits on Dec 4, 2013
  1. Sean Cribbs

    Merge pull request #462 from basho/sdc-vclock-eqc

    seancribbs authored
    Add EQC statem property for vclock. [rebased]
  2. Russell Brown
Commits on Dec 3, 2013
  1. Sean Cribbs
  2. Sean Cribbs
  3. Sean Cribbs
  4. Sean Cribbs
  5. Sean Cribbs
  6. Sean Cribbs
  7. Sean Cribbs

    eunit-ify the vclock_qc

    seancribbs authored
  8. Sean Cribbs
Commits on Nov 27, 2013
  1. Scott Lystig Fritchie
Commits on Nov 21, 2013
  1. Jordan West
  2. Jordan West

    increase broadcast's initial eager set size for larger clusters

    jrwest authored
    increasing the fanout reduces the chance of requiring exchange to deliver
    messages to all alive nodes during a broadcast. This patch decreases the
    likelyhood by 20 to 30 percent, on average.
    The chosen fanout is determined by the discrete function
    `round(log(NumNodes)+1)`, where `log(x)` is the natural log and `NumNodes`
    is the number of nodes in the cluster.  For practical cluster sizes,
    this curve has a maximum fanout of about six peers, dependning on what
    is considered the upper limit of practical cluster sizes.
    addresses #438
Something went wrong with that request. Please try again.