pjfanning commented on issue #414: URL: https://github.com/apache/pekko-management/issues/414#issuecomment-2805072252
Thanks @lomigmegard - this also affects scaling down when pod clusters have their pod counts reduced. We can't copy the Akka change. If someone has time to produce an equivalent change that would be useful. I haven't looked at the cluster code but I presume based on the description in the Akka issue that the singletons will move to the next oldest cluster member if the oldest one is stopped. I wonder if it would also be possible to set the pod deletion cost based on knowledge of whether a Pekko cluster member has singletons deployed on it. Our docs don't exactly encourage the use of singletons. Users should consider if they can rearchitect their applications to avoid relying on them. https://pekko.apache.org/docs/pekko/current/typed/cluster-singleton.html#introduction -- 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
