Skip to content

Conversation

Aaronontheweb
Copy link
Member

@Aaronontheweb Aaronontheweb commented Jun 8, 2018

Designed to reproduce and fix #3413

@@ -534,7 +534,7 @@ internal static void InitPhaseActorSystemTerminate(ActorSystem system, Config co
// We must spawn a separate Task to not block current thread,
// since that would have blocked the shutdown of the ActorSystem.
var timeout = coord.Timeout(PhaseActorSystemTerminate);
return Task.Run(() =>
Task.Run(() =>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not supposed to return a Task here. Supposed to just let the process run asynchronously and invoke once the ActorSystem has finished terminating.

{
// forces downstream error propagation if recover is disabled
var force = tr.Result;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let the task run asynchronously, but still propagate failures downstream.

@Aaronontheweb
Copy link
Member Author

@Horusiath thanks for the suggestions; was able to reproduce the issue with #3413 - I think I can TDD it from here.

@Aaronontheweb Aaronontheweb force-pushed the fix-3413-coordinated-shutdown-clusterdaemon branch from e7439de to d8d80de Compare June 11, 2018 18:19
@Aaronontheweb Aaronontheweb mentioned this pull request Jun 25, 2018
@Aaronontheweb
Copy link
Member Author

Looks like it's the reproduction spec for this that's failing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: ClusterDaemon doesn't stop upon CoordinatedShutdown
1 participant