beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafael Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (BEAM-1735) Retry 403:rateLimitExceeded in GCS
Date Tue, 21 Mar 2017 04:41:41 GMT

     [ https://issues.apache.org/jira/browse/BEAM-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rafael Fernandez updated BEAM-1735:
-----------------------------------
    Comment: was deleted

(was: Customer issue -- see more in buganizer.

Thanks!
r

On Tue, Mar 21, 2017 at 3:59 AM Daniel Halperin (JIRA) <jira@apache.org>
wrote:


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

Daniel Halperin commented on BEAM-1735:
---------------------------------------

Can you provide more information about this bug, [~rfernand]?

Most importantly: Can you provide a minimal reproduction?

If not, some additional Qs:
* How do you know this is not retried?
* Do you have a link to specific affected code?
* Which part of the codebase is this in? There are many places in which the
GCP-related code interacts with GCS.

should be retried exponentially. We currently do not retry it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
)

> Retry 403:rateLimitExceeded in GCS
> ----------------------------------
>
>                 Key: BEAM-1735
>                 URL: https://issues.apache.org/jira/browse/BEAM-1735
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-gcp
>            Reporter: Rafael Fernandez
>            Assignee: Daniel Halperin
>
> The GCS documentation [1] states that rateLimitExceeded, a 403 error, should be retried
exponentially. We currently do not retry it.
> [1] https://cloud.google.com/storage/docs/json_api/v1/status-codes 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message