You're using the word "client" where the Redis community uses the word "slave".
Good coverage of strong consistency can be found in the Redis documentation for the WAIT command:
https://redis.io/commands/waitThe notable part is in the section titled "
Consistency and WAIT":Note that WAIT does not make Redis a strongly consistent store
Since Redis slaves are always connected to the master, and replication data transfers are initiated by the master, there is no "polling interval" to configure. There is additional information in the documentation page that describes Redis replication:
https://redis.io/topics/replicationThere are network architectures that can prevent any software from meeting a "max delay of x ms" requirement. A typical example is replicating between servers that are located 3,000 miles apart, such as the US West and East Coasts. On good days the one-way propagation delay is 30-40 ms (60-80 ms round trip), but when a long-distance provider has an outage, the delays can go higher. A software architect must account for these kinds of unavoidable delays in specifying the nodes of the cluster and the cluster's consistency requirements.
By the way, it's a very good practice to perform only writes on the master node(s) and perform reads on the slave nodes, but Redis does not require it. Keys can be read from the master node too.