fredfp commented on issue #578: URL: https://github.com/apache/pekko/issues/578#issuecomment-2122284299
This bug should hit quite seldom, if it happens often it most likely means something is not right with your cluster and you should fix that first in all cases. Especially, make sure: - there's always available CPU for the cluster managment duties - not to use pekko's internal thread pool for your own workloads - make rolling update slower so that cluster is less unstable during rolling updates. -- 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: notifications-unsubscr...@pekko.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
