You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andrei Dulvac (Jira)" <ji...@apache.org> on 2020/02/13 14:52:00 UTC

[jira] [Assigned] (SLING-9053) Implement retries mechanism for AbstractSlingClient.doRequest(...)

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

Andrei Dulvac reassigned SLING-9053:
------------------------------------

    Assignee: Andrei Dulvac

> Implement retries mechanism for AbstractSlingClient.doRequest(...)
> ------------------------------------------------------------------
>
>                 Key: SLING-9053
>                 URL: https://issues.apache.org/jira/browse/SLING-9053
>             Project: Sling
>          Issue Type: Improvement
>          Components: Apache Sling Testing Clients
>    Affects Versions: Apache Sling Testing Clients 1.2.4
>            Reporter: Thierry Ygé
>            Assignee: Andrei Dulvac
>            Priority: Critical
>             Fix For: Apache Sling Testing Clients 1.2.6
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> In cloud environment, it is likely to have 503 or broken connection at a very low rate <1% of requests. This add unwanted flakiness to tests.
> Generally 503 or broken connection should be retried (at least that is recommended), thus it would be nice to introduce it on the AbstractSlingClient.doRequest(...) which seems to be the best place as common code (doGet, doPost etc..).



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