You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is ok to add some jitter when uploading blocks. The question is, do we add jitter to the shipper itself? I understand we want to jitter the caller loop. For example, in sidecar we will add it here.
Is your proposal related to a problem?
Currently, all sidecars upload blocks at the same time.
It make huge bandwidth usage to object storage.
It will be a problem when you run sidecars in on-premises and use public cloud object storage
because the dedicated line has limited bandwidth.
Describe the solution you'd like
I propose add some random delay before uploading blocks.
Let's dd the
--shipper.upload-jitter
flag.When sidecar upload blocks, it sleep random time between 0 and jitter.
Describe alternatives you've considered
I tried to manage QoS, but it's very hard to config.
The text was updated successfully, but these errors were encountered: