Mirroristas/etcd

Fork 0

mirror of https://github.com/etcd-io/etcd.git synced 2024-09-27 06:25:44 +00:00

Commit Graph

Author	SHA1	Message	Date
Piotr Tabor	0a972a3f05	applyV2 should reapply on backend only once 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.	2021-05-18 20:55:05 +02:00
Piotr Tabor	aaf423e962	server: Update imports. find -name '*.go' \| xargs sed -i --follow-symlinks 's\|etcd/v3/\|etcd/server/v3/\|g'	2020-10-26 13:02:32 +01:00
Piotr Tabor	4a5e9d1261	server: Move server files to 'server' directory. 26 git mv mvcc wal auth etcdserver etcdmain proxy embed/ lease/ server 36 git mv go.mod go.sum server	2020-10-26 12:57:19 +01:00

Author

SHA1

Message

Date

Piotr Tabor

0a972a3f05

applyV2 should reapply on backend only once

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.

2021-05-18 20:55:05 +02:00

Piotr Tabor

aaf423e962

server: Update imports.

find -name '*.go' | xargs sed -i --follow-symlinks 's|etcd/v3/|etcd/server/v3/|g'

2020-10-26 13:02:32 +01:00

Piotr Tabor

4a5e9d1261

server: Move server files to 'server' directory.

26  git mv mvcc wal auth etcdserver etcdmain proxy embed/ lease/ server
   36  git mv go.mod go.sum server

2020-10-26 12:57:19 +01:00

3 Commits