[
https://issues.apache.org/jira/browse/FLINK-22134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319405#comment-17319405
]
Robert Metzger commented on FLINK-22134:
----------------------------------------
Thanks a lot for testing this feature and for your feedback!
Quick responses on some of your items:
B1: This is documented as a limitation
B2: If you just enable reactive mode, the resource stabilization timeout should
automatically be set to 0, and you shouldn't see these issues.
Documentation: I'll file a ticket to adjust the docs.
UI 1: I'll file a ticket to adjust this; and document it as a limitation for
now.
UI 2: I guess this is not a complicated change, but one that will touch many
places in the code. I'd like to hear Chesnays and Tills input on this one as
well. Maybe we could track "Restarts" (always increasing) and "FailureRestarts"
(increasing on failures) instead of Attempts?
L1: This should have been fixed by FLINK-21558 already [~chesnay] can you take
a look?
> Test the reactive mode
> ----------------------
>
> Key: FLINK-22134
> URL: https://issues.apache.org/jira/browse/FLINK-22134
> Project: Flink
> Issue Type: Test
> Components: Runtime / Coordination
> Affects Versions: 1.13.0
> Reporter: Till Rohrmann
> Assignee: Xintong Song
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.13.0
>
> Attachments: 截屏2021-04-12 上午10.30.25.png, 截屏2021-04-12 上午10.32.50.png
>
>
> The newly introduced reactive mode (FLINK-10407) allows Flink to make use of
> newly arriving resources while the job is running. The feature documentation
> with the current set of limitations can be found here [1].
> In order to test this new feature I recommend to follow the documentation and
> to try it out wrt the stated limitations. Everything which is not explicitly
> contained in the set of limitations should work.
> [1]
> https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/elastic_scaling/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
