Open Stack

Matthew Booth <mbooth at redhat.com> wrote:

> This means that even for 'synchronous' slaves, if a client makes an RPC
> call which writes a row to write master A, then another RPC call which
> expects to read that row from synchronous slave node B, there's no
> default guarantee that it'll be there.


Can I get some kind of clue as to how common this use case is?     This is where we get into things like how nova.objects works and stuff, which is not my domain.    We are going through a huge amount of thought in order to handle this use case but I’m not versed in where / how this use case exactly happens and how widespread it is.