Skip to content

Tags: zehonghuang/openraft

Tags

v0.6.4

Toggle v0.6.4's commit message
ci: v0.6.4

v0.6.3

Toggle v0.6.3's commit message
ci: fix changelog path for 0.6.3

v0.6.2

Toggle v0.6.2's commit message
ci: build pre-release with prepared change log

v0.6.2-alpha.14.1

Toggle v0.6.2-alpha.14.1's commit message
fix: a restarted follower should not wait too long to elect. Otherwis…

…e the entire cluster hangs

v0.6.2-alpha.16

Toggle v0.6.2-alpha.16's commit message
doc: update bug fixed in README

v0.6.2-alpha.15

Toggle v0.6.2-alpha.15's commit message
refactor: add defensive check: a PurgedMarker log should never be app…

…lied to state machine

v0.6.2-alpha.14

Toggle v0.6.2-alpha.14's commit message
fix: RaftCore.entries_cache is inconsistent with storage. removed it.

- When leader changes, `entries_cache` is cleared.
  Thus there may be cached entries wont be applied to state machine.

- When applying finished, the applied entries are not removed from the
  cache.
  Thus there could be entries being applied more than once.

v0.6.2-alpha.13

Toggle v0.6.2-alpha.13's commit message
fix: install snapshot req with offset GE 0 should not start a new ses…

…sion.

A install-snapshot always ends with a req with data len to be 0 and
offset GE 0.
If such a req is re-sent, e.g., when timeout, the receiver will try to
install a snapshot with empty data, if it just finished the previous
install snapshot req(`snapshot_state` is None) and do not reject a
install snapshot req with offset GE 0.
Which results in a `fatal storage error`, since the storage tries to
decode an empty snapshot data.

- feature: add config `install_snapshot_timeout`.

v0.6.2-alpha.12

Toggle v0.6.2-alpha.12's commit message
refactor: upgrade logging level for important state changing event

v0.6.2-alpha.11

Toggle v0.6.2-alpha.11's commit message
refactor: add logs for every event leader receives.