[
https://issues.apache.org/jira/browse/FLINK-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhijiang updated FLINK-13753:
-----------------------------
Description:
This is the umbrella issue for integrating new source operator with mailbox
model in StreamTask.
The motivation is based on
[FLIP-27|https://cwiki.apache.org/confluence/display/FLINK/FLIP-27%3A+Refactor+Source+Interface]
which proposes to refactor the whole source API and the integration of
task-level actions (including checkpoint, timer, async operator) with unified
mailbox model on runtime side.
* The benefits are simple unified processing logics because only one single
thread handles all the actions without concurrent issue, and further getting
rid of lock dependency which causes unfair lock concern in checkpoint process.
* We still need to support the current legacy source in some releases which
would probably be used for a while, especially for the scenario of performance
concern.
The design doc is
[https://docs.google.com/document/d/13x9M7k1SRqkOFXP0bETcJemIRyJzoqGgkdy11pz5qHM/edit#|https://docs.google.com/document/d/13x9M7k1SRqkOFXP0bETcJemIRyJzoqGgkdy11pz5qHM/edit]
was:
This is the umbrella issue for integrating new source operator with mailbox
model in StreamTask.
The motivation is based on
[FLIP-27|https://cwiki.apache.org/confluence/display/FLINK/FLIP-27%3A+Refactor+Source+Interface]
which proposes to refactor the whole source API and the integration of
task-level actions (including checkpoint, timer, async operator) with unified
mailbox model on runtime side.
* The benefits are simple unified processing logics because only one single
thread handles all the actions without concurrent issue, and further getting
rid of lock dependency which causes unfair lock concern in checkpoint process.
* We still need to support the current legacy source in some releases which
would probably be used for a while, especially for the scenario of performance
concern.
The design doc is
[https://docs.google.com/document/d/13x9M7k1SRqkOFXP0bETcJemIRyJzoqGgkdy11pz5qHM/edit#|https://docs.google.com/document/d/13x9M7k1SRqkOFXP0bETcJemIRyJzoqGgkdy11pz5qHM/edit]|[https://docs.google.com/document/d/13x9M7k1SRqkOFXP0bETcJemIRyJzoqGgkdy11pz5qHM/edit#|https://docs.google.com/document/d/13x9M7k1SRqkOFXP0bETcJemIRyJzoqGgkdy11pz5qHM/edit]
> Integrate new Source Operator with Mailbox Model in StreamTask
> --------------------------------------------------------------
>
> Key: FLINK-13753
> URL: https://issues.apache.org/jira/browse/FLINK-13753
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Reporter: zhijiang
> Assignee: zhijiang
> Priority: Minor
>
> This is the umbrella issue for integrating new source operator with mailbox
> model in StreamTask.
> The motivation is based on
> [FLIP-27|https://cwiki.apache.org/confluence/display/FLINK/FLIP-27%3A+Refactor+Source+Interface]
> which proposes to refactor the whole source API and the integration of
> task-level actions (including checkpoint, timer, async operator) with unified
> mailbox model on runtime side.
> * The benefits are simple unified processing logics because only one single
> thread handles all the actions without concurrent issue, and further getting
> rid of lock dependency which causes unfair lock concern in checkpoint process.
> * We still need to support the current legacy source in some releases which
> would probably be used for a while, especially for the scenario of
> performance concern.
> The design doc is
> [https://docs.google.com/document/d/13x9M7k1SRqkOFXP0bETcJemIRyJzoqGgkdy11pz5qHM/edit#|https://docs.google.com/document/d/13x9M7k1SRqkOFXP0bETcJemIRyJzoqGgkdy11pz5qHM/edit]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
