mirror of
https://gitee.com/iresty/apisix.git
synced 2024-12-15 01:11:58 +08:00
dd6ee5e99f
There is a potential concurrency problem in all admin PATCH APIs when two patch requests come in simultaneously, in such case, the patched result of the first applied request will be overridden, also the probability is tidy, but from the perspective of software's robust, that's not what we wanna to see. In this commit, we use the optimistic locking to avoid this problem, for the example aforementioned, the second PATCH request will failure, and it's up to the user to retry this PATCH request again. The optimistic locking mechanism in ETCD v3 APIs is showed by it's transcation mechanism. Signed-off-by: tokers <zchao1995@gmail.com> |
||
|---|---|---|
| .. | ||
| balancer.t | ||
| consumers.t | ||
| delete-service.t | ||
| delete-upstream.t | ||
| global-rules.t | ||
| health-check.t | ||
| plugins-reload.t | ||
| plugins.t | ||
| routes-array-nodes.t | ||
| routes.t | ||
| schema.t | ||
| services-array-nodes.t | ||
| services-string-id.t | ||
| services.t | ||
| ssl.t | ||
| stream-routes-disable.t | ||
| stream-routes.t | ||
| token.t | ||
| upstream-array-nodes.t | ||
| upstream.t | ||