7 Commits

Author	SHA1	Message	Date
Piotr Tabor	d69e07dd3a	Verification framework and check whether cindex is not decreasing.	2022-04-22 12:32:05 +02:00
Marek Siarkowicz	1ea53d527e	server: Save consistency index and term to backend even when they decrease ... Reason to store CI and term in backend was to make db fully independent snapshot, it was never meant to interfere with apply logic. Skip of CI was introduced for v2->v3 migration where we wanted to prevent it from decreasing when replaying wal in https://github.com/etcd-io/etcd/pull/5391. By mistake it was added to apply flow during refactor in https://github.com/etcd-io/etcd/pull/12855#commitcomment-70713670. Consistency index and term should only be negotiated and used by raft to make decisions. Their values should only driven by raft state machine and backend should only be responsible for storing them.	2022-04-07 19:00:03 +02:00
ahrtr	e155e50886	rename LockWithoutHook to LockOutsideApply and add LockInsideApply	2022-04-07 05:35:13 +08:00
ahrtr	bfd5170f66	add a txPostLockHook into the backend ... Previously the SetConsistentIndex() is called during the apply workflow, but it's outside the db transaction. If a commit happens between SetConsistentIndex and the following apply workflow, and etcd crashes for whatever reason right after the commit, then etcd commits an incomplete transaction to db. Eventually etcd runs into the data inconsistency issue. In this commit, we move the SetConsistentIndex into a txPostLockHook, so it will be executed inside the transaction lock.	2022-04-07 05:35:13 +08:00
horizonzy	282e4e6e88	make code more readable.	2022-01-19 22:24:49 +08:00
horizonzy	97d1f935f6	avoid always update meta term.	2021-12-29 11:23:38 +08:00
Marek Siarkowicz	5b6f4579fb	server: Rename buckets to schema	2021-07-12 15:37:21 +02:00