[GitHub] beam pull request #3507: [BEAM-2556] Add client-side throttling.

2017-07-11 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/beam/pull/3507


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] beam pull request #3507: [BEAM-2556] Add client-side throttling.

2017-07-06 Thread cph6
GitHub user cph6 opened a pull request:

https://github.com/apache/beam/pull/3507

[BEAM-2556] Add client-side throttling.

The approach used is as described in

https://landing.google.com/sre/book/chapters/handling-overload.html#client-side-throttling-a7sYUg
. By backing off individual workers in response to high error rates, we 
relieve
pressure on the Datastore service, increasing the chance that the workload 
can
complete successfully.

The exported cumulativeThrottledSeconds could also be used as an autoscaling
signal in future.

R: @vikkyrk 
R: @ssisk 

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

$ git pull https://github.com/cph6/beam datastore_adaptive

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

https://github.com/apache/beam/pull/3507.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 #3507


commit 152fa5c8b8b37e3ecf1b28bacd4d636936a3ea04
Author: Colin Phipps 
Date:   2017-06-26T13:34:19Z

Add client-side throttling.

The approach used is as described in

https://landing.google.com/sre/book/chapters/handling-overload.html#client-side-throttling-a7sYUg
. By backing off individual workers in response to high error rates, we 
relieve
pressure on the Datastore service, increasing the chance that the workload 
can
complete successfully.

The exported cumulativeThrottledSeconds could also be used as an autoscaling
signal in future.




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---