Re: [PR] [fix] [broker] PulsarRegistrationClient writableBookieInfo cache and readOnlyBookieInfo cache update fail causing broker to misjudge that the bookie is unavailable [pulsar]

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

merlimat commented on PR #23021:
URL: https://github.com/apache/pulsar/pull/23021#issuecomment-6351432793

   Thanks @yyj8 for reporting this and for the patch, and sorry it sat so long. The gap is real when reading the bookie info fails while handling the registration notification: nothing retries until the next bookie change or session event. This patch doesn't wait on the `readBookieInfoAs*` futures, though, and it no longer compiles after the slog migration. I opened #27052, which reloads the info in the background on a miss and adds a deterministic test. Closing this one in favor of it.


-- 
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@pulsar.apache.org

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