Permalink
Commits on May 15, 2015
  1. Merge pull request #91 from seomoz/vadim/add-fan-out-helper

    vadim
    vadim committed May 15, 2015
    add Step::run_if? to make job elimination explicit
  2. review feedback

    vadim suvorov
    vadim suvorov committed May 15, 2015
Commits on May 14, 2015
  1. add Step::run_if? to make elimination explicit

    vadim suvorov
    vadim suvorov committed May 14, 2015
  2. set default ruby version

    vadim suvorov
    vadim suvorov committed May 14, 2015
Commits on May 7, 2015
  1. Merge pull request #90 from seomoz/address-cancellation-timeouts

    andrewbeesides committed May 7, 2015
    Address cancellation timeouts.
  2. Fixing line with > 80 chars

    Andrew Yang
    Andrew Yang committed May 7, 2015
  3. Address cancellation timeouts.

    myronmarston committed May 7, 2015
    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. Merge pull request #89 from seomoz/fix-endlessly-retried-jobs

    myronmarston committed May 5, 2015
    Fix endlessly retried jobs
  2. Do not endless retry jobs for job batches that were aborted during cr…

    myronmarston committed May 5, 2015
    …eation.
  3. Move `#perform` context out from under `#depends_on` context.

    myronmarston committed May 5, 2015
    It never belonged there.
Commits on Apr 21, 2015
  1. Merge pull request #88 from seomoz/remove-unnecessary-fanout

    myronmarston committed Apr 21, 2015
    Remove unnecessary `fan_out`.
  2. Remove unnecessary `fan_out`.

    myronmarston committed Apr 21, 2015
    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. Merge pull request #87 from seomoz/atomic-followups-part-2

    myronmarston committed Apr 17, 2015
    Atomic followups part 2
Commits on Apr 16, 2015
  1. Remove extraneous `In` from class name.

    myronmarston committed Apr 16, 2015
  2. Merge pull request #86 from seomoz/atomic-followups

    myronmarston committed Apr 16, 2015
    Atomic followups
  3. Add support for forced cancellation.

    myronmarston committed Apr 16, 2015
    This bypasses the “is the job batch still being created in
    another process” check, so use with care.
  4. Support pipelines that privatize `enqueue_jobs_for`.

    myronmarston committed Apr 16, 2015
  5. Fix return values when using atomically_start_job_batches.

    myronmarston committed Apr 16, 2015
    We want it to conform to the return values a caller would
    have had before they switched to using this new API.
  6. Merge pull request #85 from seomoz/start-job-batches-atomically

    myronmarston committed Apr 16, 2015
    Start job batches atomically
  7. Leverage the `unpause` method.

    myronmarston committed Apr 16, 2015
Commits on Apr 15, 2015
  1. Provide a way to atomically start multiple job batches.

    myronmarston committed Apr 15, 2015
  2. Address Ruby warning.

    myronmarston committed Apr 15, 2015
Commits on Apr 9, 2015
  1. Merge pull request #84 from seomoz/fix-jbl-enumeration-perf

    myronmarston committed Apr 9, 2015
    Perf optimization.
  2. Perf optimization.

    myronmarston committed Apr 9, 2015
    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. Merge pull request #82 from seomoz/support-large-batches

    myronmarston committed Mar 18, 2015
    Support large batches
  2. Fix typo.

    myronmarston committed Mar 18, 2015
    [ci skip]
  3. Allow large job batches to be deleted.

    myronmarston committed Mar 12, 2015
Commits on Mar 17, 2015