[
https://issues.apache.org/jira/browse/BEAM-12272?focusedWorklogId=603354&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-603354
]
ASF GitHub Bot logged work on BEAM-12272:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 28/May/21 01:12
Start Date: 28/May/21 01:12
Worklog Time Spent: 10m
Work Description: nehsyc commented on a change in pull request #14723:
URL: https://github.com/apache/beam/pull/14723#discussion_r641089715
##########
File path: sdks/python/apache_beam/io/gcp/datastore/v1new/datastoreio.py
##########
@@ -276,15 +277,33 @@ class _Mutate(PTransform):
Only idempotent Datastore mutation operations (upsert and delete) are
supported, as the commits are retried when failures occur.
"""
- def __init__(self, mutate_fn):
+
+ # Default hint for the expected number of workers in the ramp-up throttling
+ # step for write or delete operations.
+ _DEFAULT_HINT_NUM_WORKERS = 500
Review comment:
Thanks for bumping this! I indeed missed the edits above.
It also appears weird to me that Dataflow didn't upscale for two hours
despite the plateaued throttling time. My best guesses would be that the
workers didn't report much progress causing Dataflow to stick to the initial
scaling of the job, or the low CPU utilization prevented Dataflow to upscale.
My previous concern about reporting throttling signals was mainly the slow
ramp-up of number of workers especially when we started with very little budget
for each worker. If that is not as concerning as I imagined then I vote for
reporting `throttling-msecs`.
Most Dataflow pipelines start with a small number of workers (<10) so by
setting the default value to 500 we almost always over-constrain the rate by a
lot at the beginning. Maybe consider lowering it.
I am not familiar with how counters work in Python. Maybe @chamikaramj can
comment more on that.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 603354)
Time Spent: 3h 40m (was: 3.5h)
> Python - Backport FirestoreIO connector's ramp-up to DatastoreIO connector
> --------------------------------------------------------------------------
>
> Key: BEAM-12272
> URL: https://issues.apache.org/jira/browse/BEAM-12272
> Project: Beam
> Issue Type: Improvement
> Components: io-py-gcp
> Reporter: Daniel Thevessen
> Assignee: Daniel Thevessen
> Priority: P2
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> The FirestoreIO connector (BEAM-8376) for the Java SDK is currently out for
> review.
> Some of the features for the Firestore connector are new relative to the
> Datastore connector, so the Firestore team would like to add them there as
> well. Most notably the Firestore connector has a gradual ramp-up feature that
> slowly increases throughput in line with Datastore/Firestore best practices.
> Some minor adjustments to constants for batch sizing and backoff may also be
> worth looking at.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
