Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Tag writes are not rate limited after a TagResource or UntagResource; DynamoDB refuses a second write for several seconds

未关闭
#608 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
aws, rust
领域
backend, databases

调研方向

The issue reports inconsistent tag-write behavior across ExtendDB backends and notes that the LimitExceededException sentence is absent from crates, but it does not name a specific file or test. Start by locating the DynamoDB TagResource and UntagResource handlers and the backend tests for tag operations. Reproduce an immediate second tag write and verify it is rejected for several seconds, then accepted later; also check the reported DeleteTable behavior.

由索引模型根据 Issue 内容生成。

描述

bug

Summary

For several seconds after a TagResource or UntagResource on a table, Amazon DynamoDB refuses another tag write on the same resource with 400 LimitExceededException Subscriber limit exceeded: Table tags are being updated: <name>. ExtendDB accepts the second write at once on every backend.

Measured (us-east-1, 2026-10-26)

Request Service ExtendDB
UntagResource sent right after a TagResource on the same table (seven rows across two probe runs) 400 LimitExceededException Subscriber limit exceeded: Table tags are being updated: <name> 200
the same, 3 to 5 s later 200 200
DeleteTable sent right after a TagResource on the table (seen once) 400 ResourceInUseException Attempt to change a resource which is still in use: Table tags are being updated: <name> 200

The DeleteTable refusal was observed once; three rounds would settle it.

Notes

The LimitExceededException sentence is absent from crates. The window applies to the resource's tag set, stream ARNs included. A client that tags a table and deletes it in one script meets both refusals on the service and neither here.

主要语言
Rust
星标
517
派生
60
平均合并
2 天 22 小时
30 天内合并 PR
25

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ExtendDB/extenddb 的其他 Issue

查看 ExtendDB/extenddb 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。