When you run with real-time replication (e.g. 3), how does Druid determine which one wins the race to deep storage?
I ask because we had a task stuck in pending for a few minutes. It eventually got a slot, but it was missing those first few minutes of data. When the broker sent queries to that task, Pivot showed a noticeable gap. We now kill any duplicate tasks that get stuck in pending, but I’d like to understand better what happens during segment persist on real-time tasks.
(pointers to code work =)