One way to resolve it is to mark that user or session (or even just request) "sticky to the master" for long enough to cover your normal replication delay. Whe

One way to resolve it is to mark that user or session (or even just request) "sticky to the master" for long enough to cover your normal replication delay. When we saw it before, ensuring that a given request which issued a write also read from the master was sufficient. (sub-second replication delay).