>>> Quanah Gibson-Mount <[email protected]> schrieb am 22.06.2022 um 17:29 in Nachricht <DAC521212CF4E0B84C0B2E7B@[192.168.1.17]>:
> > ‑‑On Wednesday, June 22, 2022 9:03 AM +0200 Ulrich Windl > <[email protected]‑regensburg.de> wrote: > >> Ignoring the loadbalancer issues, I think you add a race condition when >> reading possibly older data from your consumers and maybe write them back >> where newer data may exist already (i.e.: providers). BTW: Is a modify >> operation a read, or is it a write? > > modify ops are always a write operation, since they are doing a > modification. Sorry, I was not precise enough: What I wanted to ask was: Is the "modify" the user was talking about a LDIF-like modify, or is it a user-level modify like reading data from one source, manipulating the data and then write that data to a possibly different destination. The latter case is probably opening a can of worms, so to say. > > And yes, read‑after‑write can be a tricky issue to handle. > > ‑‑Quanah
