Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
imported from https://github.com/gearpump/gearpump/issues/1231 on behalf of clockfly,
DAG with loop should not be called DAG
We see use cases that require a feedback channel.
The challengues will be:
- how to support the low watermark clock? As the clock is defined recursively?
- How to support back-pressure. DAG with loop can possiblely create a live-lock issue. With each processor wait for acks from other processor before sending acks.
Attachments
Issue Links
- depends upon
-
GEARPUMP-114 Dead loop in graph with cycles
- Resolved