diff options
| author | Madelyn Olson <34459052+madolson@users.noreply.github.com> | 2022-04-26 03:25:33 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-26 13:25:33 +0300 |
| commit | 6fa8e4f7afcbd14748c736c38e5fbc117eaef7ba (patch) | |
| tree | e74b7ddf889b99daadd615cbee5ca069e14c82bb /tests/unit/pubsubshard.tcl | |
| parent | efcd1bf394668e418df1a93cd28cf9e8b0c09ce5 (diff) | |
| download | redis-6fa8e4f7afcbd14748c736c38e5fbc117eaef7ba.tar.gz | |
Set replicas to panic on disk errors, and optionally panic on replication errors (#10504)
* Till now, replicas that were unable to persist, would still execute the commands
they got from the master, now they'll panic by default, and we add a new
`replica-ignore-disk-errors` config to change that.
* Till now, when a command failed on a replica or AOF-loading, it only logged a
warning and a stat, we add a new `propagation-error-behavior` config to allow
panicking in that state (may become the default one day)
Note that commands that fail on the replica can either indicate a bug that could
cause data inconsistency between the replica and the master, or they could be
in some cases (specifically in previous versions), a result of a command (e.g. EVAL)
that failed on the master, but still had to be propagated to fail on the replica as well.
Diffstat (limited to 'tests/unit/pubsubshard.tcl')
0 files changed, 0 insertions, 0 deletions