Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on May 15, 2015
  1. @vadim-moz

    Merge pull request #91 from seomoz/vadim/add-fan-out-helper

    vadim-moz authored
    add Step::run_if? to make job elimination explicit
  2. @vadim-moz

    review feedback

    vadim-moz authored
Commits on May 14, 2015
  1. @vadim-moz
  2. @vadim-moz

    set default ruby version

    vadim-moz authored
Commits on May 7, 2015
  1. @andrewbeesides

    Merge pull request #90 from seomoz/address-cancellation-timeouts

    andrewbeesides authored
    Address cancellation timeouts.
  2. @andrewbeesides
  3. @myronmarston

    Address cancellation timeouts.

    myronmarston authored
    For large batches it is very painful to have a cancellation
    timeout, because it spends a long time preparing for it
    (doing a topological sort of all jobs), which forces us
    to re-do all that work when we retry. Better to have some
    simple retries in place for the actual `bulk_cancel` call.
Commits on May 5, 2015
  1. @myronmarston

    Merge pull request #89 from seomoz/fix-endlessly-retried-jobs

    myronmarston authored
    Fix endlessly retried jobs
  2. @myronmarston
  3. @myronmarston
Commits on Apr 21, 2015
  1. @myronmarston

    Merge pull request #88 from seomoz/remove-unnecessary-fanout

    myronmarston authored
    Remove unnecessary `fan_out`.
  2. @myronmarston

    Remove unnecessary `fan_out`.

    myronmarston authored
    Originally, we only supported 1 fan out and it was useful
    to ensure there was a default one. Now that we support many,
    having no fan out blocks is fine. This is unnecessary and
    wasteful, so I’m removing it.
Commits on Apr 17, 2015
  1. @myronmarston

    Merge pull request #87 from seomoz/atomic-followups-part-2

    myronmarston authored
    Atomic followups part 2
Commits on Apr 16, 2015
  1. @myronmarston
  2. @myronmarston
  3. @myronmarston
  4. @myronmarston

    Merge pull request #86 from seomoz/atomic-followups

    myronmarston authored
    Atomic followups
  5. @myronmarston

    Add support for forced cancellation.

    myronmarston authored
    This bypasses the “is the job batch still being created in
    another process” check, so use with care.
  6. @myronmarston
  7. @myronmarston

    Fix return values when using atomically_start_job_batches.

    myronmarston authored
    We want it to conform to the return values a caller would
    have had before they switched to using this new API.
  8. @myronmarston

    Merge pull request #85 from seomoz/start-job-batches-atomically

    myronmarston authored
    Start job batches atomically
  9. @myronmarston
Commits on Apr 15, 2015
  1. @myronmarston
  2. @myronmarston
  3. @myronmarston

    Address Ruby warning.

    myronmarston authored
Commits on Apr 9, 2015
  1. @myronmarston
  2. @myronmarston

    Perf optimization.

    myronmarston authored
    Previously, each time we enumerated a JobBatchList, we started
    at 1 and counted up to the current counter value. This has gotten
    slower and slower over time as the value of the counter has increased.
    
    When we enumerate the list and find the first job batch at number n,
    we know that there will never again be any job batches found at
    numbers 1 through (n - 1), so we can safely skip those checks on
    future enumerations. This is a safe assumption because
    
    * New job batches get their number by incrementing the counter.
      Thus no new job batch could be created with a number lower than
      an existing job batch already has.
    * Once a job batch is no longer in redis (whether or through expiration
      or a manual delete), it will never come back.
Commits on Mar 18, 2015
  1. @myronmarston

    Merge pull request #82 from seomoz/support-large-batches

    myronmarston authored
    Support large batches
  2. @myronmarston

    Fix typo.

    myronmarston authored
    [ci skip]
  3. @myronmarston
  4. @myronmarston
  5. @myronmarston
  6. @myronmarston
Commits on Mar 17, 2015
  1. @myronmarston
  2. @myronmarston
Something went wrong with that request. Please try again.