Skip to content

fix: Cancel any replays when the filter stage stops - #1198

Open
johanandren wants to merge 2 commits into
mainfrom
wip-cancel-replays
Open

fix: Cancel any replays when the filter stage stops#1198
johanandren wants to merge 2 commits into
mainfrom
wip-cancel-replays

Conversation

@johanandren

Copy link
Copy Markdown
Contributor

No description provided.

})

override def postStop(): Unit = {
replayInProgress.values.foreach(_.queue.cancel())

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

That is via an async callback. Will that callback complete before the termination, or is that not what we are trying to do?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It's not waiting on that cancel in any way, so probably still a race, but at least somewhat less risk that any of those queue streams are still running when/if this stage stops vs not doing anything.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Ah, crap you are probably on to something, the queue:s are always submaterialized, so no chance that they will stop unless we add some logic that defers this stage from stopping.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

So to get rid of that abrupt termination error we'd need to keep the stage running here, watchTermination on any queue, so we can complete only once any replays complete :/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

hm, and there is no way to silence the abrupt termination logging for these specific stages?
we would anyway want to stop the replay as quickly as possible?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think it is the QueueSink logic doing it when there are queued elements here, I guess we could introduce some option to silence that: https://github.com/akka/akka/blob/5e9e11b5f6df03ed89c5ca37bdbb295ff5c19ec4/akka-stream/src/main/scala/akka/stream/impl/Sinks.scala#L365

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Pushed a quick stab at delaying cancellation but not sure it is worth the risk to break something.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants