[GitHub] [pinot] sajjad-moradi commented on pull request #11166: Fix the issue of consuming segment entering ERROR state due to stream connection errors

["sajjad-moradi (via GitHub)" <gi...@apache.org>]

sajjad-moradi commented on PR #11166:
URL: https://github.com/apache/pinot/pull/11166#issuecomment-1650289291

   > Does it work if we directly send stop consume message when it throws exception in the constructor?
   
   That's a great idea. I actually verified that it works as expected:
   Before the problematic segment goes to ERROR state, the IS is marked as OFFLINE for the segment. For a very short period of time, the EV is in ERROR state till Helix kicks off `ERROR -> OFFLINE` transition for that segment. Then it becomes OFFLINE. After that kicking off `RealtimeSegmentValidationManager` creates a new consuming segment for the partition.


-- 
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

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