[GitHub] [kafka] guozhangwang commented on pull request #13523: MINOR: Follow-up on failing streams test, and fix StoreChangelogReader

["guozhangwang (via GitHub)" <gi...@apache.org>]

guozhangwang commented on PR #13523:
URL: https://github.com/apache/kafka/pull/13523#issuecomment-1503662179

   > Ideally, rebalancing is a temporary situation and if everything goes well we should leave that state as soon as possible.
   
   I totally agree with you @lucasbru . As I mentioned in the above comment, "before we baked in the state-updater, i.e. remove the old code and make state-updater always enabled, we decided to still honor the current behavior". After state-updater becomes the only choice, I think we should allow restoration and state-updater and processing on main thread to happen at the same time, in which case `REBALANCING` state should be pretty short-lives, if any. And for us the question becomes whether we would want a new state to indicate that some restoration is happening in parallel while we are processing.


-- 
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: jira-unsubscribe@kafka.apache.org

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