Support duration based retries
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
该 issue 未指明要检查的文件、测试或入口点。首先定位现有的 backoff-duration 和 retry-count 配置，然后定义并测试基于持续时间的重试行为，使其在客户端指定的时间段结束后停止，并报告该持续时间。
由索引模型根据 Issue 内容生成。
描述
What happened?
Retry behavior is exposed via backoff duration and number of retries. Clients can specify waiting for up to 300ms before the first retry, up to 600ms before the next retry and so on until they run out retries.
Clients should think about how long they're willing to try rather than how many times they are willing to try. For example, an interactive dashboards are willing to retry for up to 10 seconds whereas long-running pipelines are willing to retry up to 20 minutes. While we can approximate this behavior with the existing controls by tuning the backoff duration and retry count, we're tuning a distribution, not a specific duration. For example, the expected time spent retrying could be 20 minutes but if we're unlucky, the total time spent retrying could be less than 2 minutes. This leads to clients that are pathologically overly sensitive to 429s from the server.
What did you want to happen?
Support duration based retries where the client specifies how long they're willing to retry. This allows the client to express their retry contract in a consistent, easy to understand way. We still get all the benefits of employing jitter to stagger retries, but the implementation details are hidden away from the client. The client tries for 20 minutes and then gives up saying that it has tried for 20 minutes. This means a lot more than giving up saying that it has tried 10 times.
- 主要语言
- Java
- 星标
- 96
- 派生
- 95
- 平均合并
- 8 分钟
- 30 天内合并 PR
- 55
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
palantir/conjure-java-runtime 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 48/100
palantir/conjure-java-runtime#3585 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 50/100
palantir/conjure-java-runtime#3166 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 45/100
palantir/conjure-java-runtime#2248 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
palantir/conjure-java-runtime#2131 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 42/100
palantir/conjure-java-runtime#1882 · 1 个 reaction ·
维护者通常 1 天内回复
查看 palantir/conjure-java-runtime 的全部 Issue
相似的 Issue
-
needs-area-label
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 2 天内回复
-
enhancement Java macOS
难度 2/5 1-3 小时 新手友好度 78/100
freerouting/freerouting#1079 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
apache/maven-enforcer#1074 ·
维护者通常 1 天内回复
-
Gradle liquibaseDiffChangelog drops jhi_date_time_wrapper可能已有人在做 @mraible 今天认领。 未关闭area: triage theme: undefined
难度 2/5 1-3 小时 新手友好度 88/100
jhipster/generator-jhipster#35998 ·
维护者通常 1 天内回复