Revision c4ebac0c5744591c4ab532d626efeb808d97e7a2 authored by Piotr Tabor on 18 May 2021, 18:00:55 UTC, committed by Gyuho Lee on 19 May 2021, 06:16:59 UTC
During review of: https://github.com/etcd-io/etcd/pull/12988 spotted that PUT is actially writing to v3-backend. If we are replaying WAL log, it might happened that backend's applied_index is > than the WAL's log entry. In such situation we should skip applying on backend V3. I think both the methods (setVersion, setMembersAttributes) are in practice idempotent so its not that 'serious' problem, but for formal correctness adding the proper checks.
1 parent 379c361
| File | Mode | Size |
|---|---|---|
| benchmark | ||
| insta-discovery | ||
| kubernetes-deploy | ||
| patch | ||
| tls-setup | ||
| README.md | -rw-r--r-- | 43 bytes |
Computing file changes ...
