beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dhalperi <...@git.apache.org>
Subject [GitHub] incubator-beam pull request #917: [BEAM-383] BigQuery: limit max job polling...
Date Sun, 04 Sep 2016 22:11:58 GMT
GitHub user dhalperi opened a pull request:

    https://github.com/apache/incubator-beam/pull/917

    [BEAM-383] BigQuery: limit max job polling time to 1 minute

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    Before the backoff would grow unboundedly, so we could in principle wait
    1.5x to 2x the actual job time. For long running jobs this is hours.
    Now, we just back off at most 1 minute between checking the job state.
    Note there should be no danger of QPS overload here because we should
    have very few concurrent outstanding jobs

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dhalperi/incubator-beam bigquery-write-backoff

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-beam/pull/917.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #917
    
----
commit 0cc46575c32fc5f96b9ec0a488b639d8ea105b99
Author: Dan Halperin <dhalperi@google.com>
Date:   2016-09-04T21:54:42Z

    BigQuery: limit max job polling time to 1 minute
    
    Before the backoff would grow unboundedly, so we could in principle wait
    1.5x to 2x the actual job time. For long running jobs this is hours.
    Now, we just back off at most 1 minute between checking the job state.
    Note there should be no danger of QPS overload here because we should
    have very few concurrent outstanding jobs

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message