wenbingshen commented on PR #3495: URL: https://github.com/apache/bookkeeper/pull/3495#issuecomment-1281747548
> IMO, we should keep the session expired policy as `reconnect` because Bookie is a heavy service with the state, and shutdown it when the session expired, will cause the BookKeeper cluster unstable. Yes. I think we can introduce these two polices and keep `reconnect` as the default policy. When users encounter the instability of the bookie service due to session expiration, they can adjust to the `shutdown` policy, such as @dlg99's comment at https://github.com/ apache/bookkeeper/issues/3250#issuecomment-1190996890. > In Pulsar, we have changed the default session expired policy from `shutdown` to `reconnect` to make the Pulsar service more stable. Yes, I believe this makes sense as long as the reconnect policy matures. > Currently, Bookie has issues with session expired, and we should enhance the reconnect policy instead of introducing a shutdown policy. We can keep the reconnect policy as the default, and provide a shutdown policy option until the `reconnect` is perfected and stabilized. @hangc0276 PTAL. -- 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]
