zrepl/replication
Christian Schwarz 45373168ad replication: fix retry wait behavior
An fsrep.Replication is either Ready, Retry or in a terminal state.
The queue prefers Ready over Retry:

Ready is sorted by nextStepDate to progress evenly..
Retry is sorted by error count, to de-prioritize filesystems that fail
often. This way we don't get stuck with individual filesystems
and lose other working filesystems to the watchdog.

fsrep.Replication no longer blocks in Retry state, we have
replication.WorkingWait for that.
2018-10-19 17:23:00 +02:00
..
fsrep replication: fix retry wait behavior 2018-10-19 17:23:00 +02:00
internal replication: fix retry wait behavior 2018-10-19 17:23:00 +02:00
pdu replication: regenerate pdu.pb with new protoc-gen-go 2018-10-13 17:23:39 +02:00
context.go gofmt 2018-08-25 21:30:25 +02:00
mainfsm.go replication: fix retry wait behavior 2018-10-19 17:23:00 +02:00
state_enumer.go replication: simpler PermanentError state + handle context cancellation 2018-10-19 17:23:00 +02:00