# About proper distributed AbortCheck

**URL:** https://discourse.vtk.org/t/about-proper-distributed-abortcheck/16315
**Category:** Development
**Created:** [March 5, 2026, 3:56pm UTC](https://discourse.vtk.org/t/about-proper-distributed-abortcheck/16315 "2026-03-05T15:56:35Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.vtk.org/user_avatar/discourse.vtk.org/mwestphal/32/19_2.png) [@mwestphal](https://discourse.vtk.org/u/mwestphal)
#### Post date: [August 26, 2026, 8:38am UTC](https://discourse.vtk.org/t/about-proper-distributed-abortcheck/16315/7 "2026-08-26T08:38:25Z")

</div>

Duplicating my answer here: [Improving Abort Functionality in VTK](https://discourse.vtk.org/t/improving-abort-functionality-in-vtk/7813)

I’m afraid it may not be a nice as he would have hoped but here it is (read [https://gitlab.kitware.com/vtk/vtk/-/work\_items/18463](https://gitlab.kitware.com/vtk/vtk/-/work_items/18463) first) :

The current abort implementation is merely a `CheckAbort` being repeatedly called at high velocity in the filters. This is problematic because there is no way to call `SetAbortExecute` while the filter execute in a distributed way.

Applications however rely on the rank 0 sending progress events to track progress of filters, and executing code on rank 0 during a progress event is possible, which of course include calling `SetAbortExecute`.

So once rank 0 has the abort flag, how to transmit it to other ranks ?

Well, the idea is of course to send it from rank 0 to other ranks, **but it is not VTK responsability to do that.**

VTK is merely responsible to signal to applications that each rank is currently checking the abort flag.

So I will introduce a `CheckAbortAndInvoke` method, that will invoke a `CheckAbort` event and then check if the abort is set.

This is the first hurdle, but then, since application uses this event to trigger multiprocess communication, we end up needing to call `CheckAbortAndInvoke` the exact same number of time on each rank, which is an unreassonnable ask.

The solution is to use another signal, at the end of the request data implementation, which can be emitted easilly using `CleanupAbortCheckEvent`.

Application are now able to cleanup any multi process communication setup that they have been using during the CheckAbort event handling.

I was able to implement that in ParaView using MPI NoBlockSend/NoBlockReceive/Test/Cancel API : [https://gitlab.kitware.com/paraview/paraview/-/merge\_requests/7921](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/7921)

Of course, it means that any VTK user willing to get the same abort support also require to implement the communication, but I’m afraid this implementation is outside of the scope of vtkAlgorithm responsabilities.

---

_[View the full topic](https://discourse.vtk.org/t/about-proper-distributed-abortcheck/16315)._