Closed FlorianDold closed 8 years ago
implementing the parallel element will fix the problem, in case every node is executing the same tasklist. tha fact that every node has to execute the same tasklist is a bit awkward in case you want to design huge experiment setups controlling nodes with different functionalities, in our case attacker and victims... so this may be a new issue and comes along with a mored detailed structures of tasks, taskslists and executors.
Barriers are implemented with the synchronize
element.
Tasklists should have to ability to specify a synchronization barrier. Execution of a tasklist only continues after a barrier if all (or a threshold of) nodes have reached the barrier.
A barrier should be a new task element in the tasklist specification, e.g.
<barrier id="foo" />
.It's not clear how barriers would interact with the
parallel
element. If we don't find any good interpretation, we should disallow thebarrier
element in all but a top-level sequential task element.Implementing this feature might entail some significant changes in the architecture of the worker queue.