[ 
https://issues.apache.org/jira/browse/HUDI-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937360#comment-16937360
 ] 

BALAJI VARADARAJAN edited comment on HUDI-269 at 9/25/19 3:12 AM:
------------------------------------------------------------------

ok, looks like there is only one file-group (but there could be multiple 
versions) and one partition in the whole dataset. So, its understandable why 
you did not see any benefits with timeline server.  With larger dataset, you 
should observe savings.


was (Author: vbalaji):
ok, looks like there is only one file and one partition in the whole dataset. 
So, its understandable why you did not see any benefits with timeline server.  
With larger dataset, you should observe savings.

> Provide ability to throttle DeltaStreamer sync runs
> ---------------------------------------------------
>
>                 Key: HUDI-269
>                 URL: https://issues.apache.org/jira/browse/HUDI-269
>             Project: Apache Hudi (incubating)
>          Issue Type: Improvement
>          Components: deltastreamer
>            Reporter: BALAJI VARADARAJAN
>            Assignee: Xing Pan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>         Attachments: hudi_request_test.tar.gz, 
> image-2019-09-25-08-51-19-686.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Copied from [https://github.com/apache/incubator-hudi/issues/922]
> In some scenario in our cluster, we may want delta streamer to slow down a 
> bit.
> so it's nice to have a parameter to control the min sync interval of each 
> sync in continuous mode.
> this param is default to 0, so this should not affect current logic.
> minor pr: [#921|https://github.com/apache/incubator-hudi/pull/921]
> the main reason we want to slow it down is that aws s3 is charged by s3 
> get/put/list requests. we don't want to pay for too many requests for a 
> really slow change table.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to