jtuglu1 commented on PR #18824: URL: https://github.com/apache/druid/pull/18824#issuecomment-3631119372
Thanks. I'm doing a bit of simulation testing to see if I can squeeze some more out. I've added the other potential one I uncovered here: ``` T0[Coordinator]: Start DutyGroup[HistoricalManagementDuties] T1[Coordinator]: Start PrepareBalancerAndLoadQueues::run() T2[Coordinator]: Move initiated of segment[S] from Server[A] to Server[B] (no callbacks yet) T3[Coordinator]: End PrepareBalancerAndLoadQueues::run() T4[Coordinator]: End DutyGroup[HistoricalManagementDuties] T5[Coordinator]: Start DutyGroup[HistoricalManagementDuties] T6[Coordinator]: Start PrepareBalancerAndLoadQueues::run() T7[Coordinator]: enter prepareCurrentServers() T8[Coordinator]: exit prepareCurrentServers() T9[Coordinator]: enter prepareCluster() T10[Coordinator-callback]: Server[B] completed request[MOVE_TO] on segment[S] with status[SUCCESS] T11[Coordinator-callback]: Dropping segment [S] from server[A] T12[A]: Completely removing segment[S] in [30,000]ms. T13[Coordinator-callback]: Server[A] completed request[DROP] on segment[S] with status[SUCCESS]. T14[Coordinator]: exit prepareCluster() // at this point, I think somehow the segmentreplicacount struct has loaded=0 (somehow which causes the other load) T15[Coordinator-callback]: Server[C] completed request[LOAD] on segment[S] with status[SUCCESS] T16[Coordinator]: End DutyGroup[HistoricalManagementDuties] ``` This causes a 2nd load -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
