anuragrai16 commented on PR #17754: URL: https://github.com/apache/pinot/pull/17754#issuecomment-3949705495
1. Can you add details on what is the current behaviour ? I believe it retries upto 5 times to create the consumer and once failed, it sends a `segmentStoppedConsuming` back to controller. Why cant increasing this retries or make it perpetual also not solve this issue ? 2. If the underlying issue persists, we have a continuous loop of : Validation → Repair (OFFLINE→CONSUMING) → Helix triggers transition → Server tries to consume → Fails → segmentStoppedConsuming → OFFLINE → Next Validation → Repair again. Im wondering what sort of race conditions can be caused by this ? And whether the server trying to start the consumption perpetually on its own and publishing a metric of retries is a safer fix ? 3. To prevent (2) happening frequently, do we wanna add a lastRepairTime - and send a new event only after x seconds/minutes ? -- 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]
