meet an inconsistency problem. redis version 5.0.4 master A → B slaveof A → C slaveof B now ，commonds cannot sync from B to C 。 why ?

Comment From: patpatbear

@seufish can you elaborate more details about how to reproduce the issue? e.g. what commands caused this inconsistency issue?

Comment From: seufish

@patpatbear Redis redis5.0.4 chained slaves inconsistency problem create replication 6379→6380→6381 ，as pic。 command "set testsync seufish" at 6380,but 6381 can't get testsync。

Comment From: patpatbear

@seufish, i think this is not an issue. from redis-3 or 4 on, all replication stream are generated by master(6379), commands executed in slave(6380) will not propagate. plus 6380 is readonly by default, normally you don't want to set 'slave-read-only' to 'no'.

Comment From: seufish

@patpatbear send you email,please check

Comment From: antirez

Yep, this is a behavior change, you can't write to a slave and have it propagated to the chained slaves anymore, but this was never intended anyway, it was more an artifact of the old replication system.