Hi Mike, Robert
Thanks for replying, the system is almost like what Mike has described: one
writer is primary,
and the other is trying to catch up and wait, but in our internal
discussion we found there might
be small chances where the secondary mistakenly think itself as primary
(due to errors
+1 trying to coordinate multiple writers running independently will
not work. My 2c for availability: you can have a single primary active
writer with a backup one waiting, receiving all the segments from the
primary. Then if the primary goes down, the secondary one has the most
recent commit
You are still talking "Multiple writers". Like i said, going down this
path (playing tricks with filenames) isn't going to work out well.
On Fri, Dec 16, 2022 at 2:48 AM Patrick Zhai wrote:
>
> Hi Robert,
>
> Maybe I didn't explain it clearly but we're not going to constantly switch
> between
