Arnaud Burlet

As reporter of https://github.com/typelevel/cats-effect/issues/3993 I'm wondering if the starvation reporter is anything special here. Errors are usually reported by printing to sdterr (e.g., `cats.effect.IOApp.onNonMainThreadDetected`), I was wondering if we should...

Usual failure reporter (i.e., `ExecutionContext#reportFailure`) have the following signature: `Throwable => Unit`, whereas for `IOApp#reportFailure` it is `Throwable => IO[Unit]`. Did you have that in mind in your comment above?...

I've seen quite a few cases where an `IORuntime`, and `Dispatcher`s are used but there's no `IOApp` anywhere. With that in mind, would it make sense to assume we'll rely...

Please have a look at this proposal, it is minimal in that: - it assumes usage of an `IOApp` (i.e., didn't check yet if the same could be achieved for...

Also, the proposed fix would need to be slightly adapted if https://github.com/typelevel/cats-effect/pull/4010 is accepted

I have extra logs that may be useful: > Remote ActorSystem must be restarted to recover from this situation. Reason: Cluster member removed, previous status [Down]

@pjfanning I think the issue can happen when a node shutsdown during a partition. Still, DownSelfQuarantinedByRemote events cannot be ignored. The root cause is that nodes should not know they...

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....

> For Kubernetes users, we would suggest using the Kubernetes Lease described here: https://pekko.apache.org/docs/pekko/current/split-brain-resolver.html#lease That's what we use already and it didn't help in the current case. Do you expect...

> @fredfp It's good to hear that using the Split Brain Resolver with a Kubernetes Lease stops all the nodes from downing themselves. Sorry, let me be clearer: using the...