[GitHub] [pinot] Jackie-Jiang opened a new issue, #8919: Reset segment might leave segment in disabled state if the controller fails to re-enable it

[GitBox <gi...@apache.org>]

Jackie-Jiang opened a new issue, #8919:
URL: https://github.com/apache/pinot/issues/8919

   In `PinotHelixResourceManager`, `resetSegment()` and `resetAllSegments()` will temporarily disable the partition if the partition state is not `ERROR`, then re-enable it after it becomes `OFFLINE`. If controller fails to re-enable the partition (restarted, encounters exception when waiting for segment to become `OFFLINE` etc.), the partition will be left disabled.
   
   To fix it, we should use the same mechanism as Helix - send a state transition message to the instance to bring it to OFFLINE state.


-- 
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: commits-unsubscribe@pinot.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org