Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: jdm-graceful-s…
Commits on Oct 2, 2012
  1. @jonmeredith
Commits on Sep 19, 2012
  1. @jonmeredith
Commits on Sep 13, 2012
  1. @jaredmorrow

    Merge pull request #223 from basho/jdb-timers

    jaredmorrow authored
    Change ticks from timer to more efficient erlang:send_after
  2. @jaredmorrow

    Merge pull request #224 from basho/adt-os-timestamp

    jaredmorrow authored
    erlang:now() -> os:timestamp() in all the places it is safe
Commits on Sep 8, 2012
  1. @jaredmorrow @Vagabond

    Update webmachine dep to bring in new mochiweb

    jaredmorrow authored Vagabond committed
  2. @Vagabond

    erlang:now() -> os:timestamp() in all the places it is safe

    Vagabond authored
    There are a few places I didn't touch as it was unclear if the values
    needed to be monotonic or not. Specifically core_claimant, core_gossip,
    core_ring and core_ring_manager.
Commits on Sep 7, 2012
  1. @jaredmorrow
Commits on Aug 29, 2012
  1. @kellymclaughlin
  2. @kellymclaughlin

    Include eunit header.

    kellymclaughlin authored
  3. @kellymclaughlin

    Add eunit test.

    kellymclaughlin authored
  4. @kellymclaughlin
  5. @kellymclaughlin
  6. @kellymclaughlin
Commits on Aug 16, 2012
  1. @jonmeredith

    Take newer upstream poolboy.

    jonmeredith authored
    @vagabond promised it works.
Commits on Aug 3, 2012
  1. @jtuple
  2. @jtuple

    Ensure legacy nodes are probed when new capabilities registered

    jtuple authored
    The capability system caches prior probes of legacy app vars when dealing
    with legacy nodes. Prior to this commit, the logic was simple. If there
    were any cached results, no probes were performed. Unfortunately, this
    could lead to a race condition. If capabilities were probed before all
    applications (eg. riak_core, riak_kv) had started and registered their
    capabilities, the cache would only include some results, and no probes
    would be performed for the newly registered capabilities. This commit
    makes things more fine-grained, checking for cached results of individual
    capabilities.
    
    This change does nothing for non-legacy nodes. All nodes that support
    the capability system natively already worked with delayed registration.
Commits on Jul 25, 2012
  1. @jtuple
  2. @jtuple

    Fix spurious "Forcing update of stalled ring"

    jtuple authored
    Changed the force update logic in riak_core_claimant to not perform
    a forced update if we have pending staged joins and no auto-joining
    nodes. Forcing a ring update because of staged joins will not actually
    change the ring, because staged joins will not transition until
    committed. This was a false positive detection of a stalled ring.
  3. @russelldb

    restructure supervision tree so that folsom is an included app

    russelldb authored
    All stat mods depend on folsom, yet they are not linked to it.
    This change brings folsom under supervision of a core stat sup,
    which also supervises the riak stat subsystem. Now when folsom exits
    everyone gets to restart clean and recover.
    
    riak_core_sup
        |
    riak_core_stat_sup (rest_for_one)
        \
           - folsom_sup
           - riak_core_stats_sup (one_for_one)
            \
              - riak_*_stat
              - riak_stat_cache
    
    riak_core_stats_sup will start and supervise gen_server stat mods at
    registration time, and will re-start them should the sup crash.
Commits on Jul 24, 2012
  1. @jtuple
  2. @jtuple
Commits on Jul 22, 2012
  1. @jtuple

    Merge pull request #214 from basho/jdb-ring-manager-load

    jtuple authored
    Fix race during start-up that could overwrite existing ring file.
    Fix issue #166.
  2. @jtuple

    Fix capability system race condition

    jtuple authored
    Prevent the node from crashing when the capability system attempts to
    negotiate capabilities before the node has registered any capabilities.
  3. @jtuple

    Make the ring manager responsible for loading the ring

    jtuple authored
    Change riak_core_ring_manager and riak_core_app so that the ring manager
    is responsible for loading the ring file from the disk rather than starting
    with an initially empty ring and then relying upon the riak_core app to
    later load the ring. This avoids a race condition with the ring manager
    writing the empty ring to the disk before the riak_core app loads the
    prior ring.
    
    Note: Riak previously relied upon starting with a fresh ring in order to
    ensure secondary vnodes were started in case any had fallback data that
    needed to be handed off. The act of starting secondaries has long since
    been moved to the riak_core_vnode_manager that periodically starts up
    secondary vnodes over time, therefore there is no longer any need to
    start with a fresh ring. This commit will therefore always load a saved
    ring when the ring_manager starts, rather than starting with a fresh ring.
Commits on Jul 20, 2012
  1. @russelldb
  2. @russelldb

    Register stat mods with the riak_core app

    russelldb authored
    When the stat cache crashes, we must re-register stat mods with
    the cache so that it works when re-started.
    
    Delete stats before register
    
    This is to ensure that a restarted riak_core_stat will not
    leave any orphaned folsom stats. Folsom needs some work to handle
    crashing owners better. Some table in folsom are owned
    by the creating process, and some by folsom. If riak_core_stat
    crashes some folsom can be left inconsistent. This cleans up
    at start time.
Commits on Jul 18, 2012
  1. @jaredmorrow
Commits on Jul 17, 2012
  1. @russelldb

    Merge pull request #210 from basho/rdb-stat-crash

    russelldb authored
    Don't crash the cache when a stat mod crashes
  2. @russelldb

    Don't crash the cache when a stat mod crashes

    russelldb authored
    Since calls to calculate stats are spawn_linked to ensure
    that the calculating processes exits if the cache exits, the cache
    will crash if a spawned process exits. This is bad. This change
    traps_exits on spawned processes and enforms awaiting callers of
    the error, without crashing the cache or effecting other registered
    mods.
Commits on Jul 13, 2012
  1. @jaredmorrow

    Fix folsom dependency

    jaredmorrow authored
  2. @jaredmorrow
  3. @jaredmorrow
  4. @jaredmorrow

    Roll version 1.2.0

    jaredmorrow authored
Commits on Jul 10, 2012
  1. @dizzyd

    Merge pull request #207 from basho/adt-monitor-leak

    dizzyd authored
    Demonitor vnode workers when they are checked back in
Commits on Jul 9, 2012
  1. @Vagabond
Something went wrong with that request. Please try again.