You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gearpump.apache.org by "Manu Zhang (JIRA)" <ji...@apache.org> on 2016/04/21 10:22:25 UTC

[jira] [Created] (GEARPUMP-78) https://github.com/gearpump/gearpump/issues/1231

Manu Zhang created GEARPUMP-78:
----------------------------------

             Summary: https://github.com/gearpump/gearpump/issues/1231
                 Key: GEARPUMP-78
                 URL: https://issues.apache.org/jira/browse/GEARPUMP-78
             Project: Apache Gearpump
          Issue Type: Improvement
          Components: streaming
            Reporter: Manu Zhang


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)