[
https://issues.apache.org/jira/browse/FLINK-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yangze Guo updated FLINK-15364:
-------------------------------
Description:
[As
discussed|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Adding-e2e-tests-for-Flink-s-Mesos-integration-td35660.html],
we need to test streaming task using heap backend. It should explicitly set the
“taskmanager.memory.managed.size” to zero to check the potential
unexpected usage of off-heap memory.
This case tests whether Flink requests workers from Mesos with proper size and
whether the dynamic properties are properly taking effect. This case also fills
the gap of real interaction with Mesos.
was:
[As
discussed|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Adding-e2e-tests-for-Flink-s-Mesos-integration-td35660.html],
we need to test streaming task using heap backend. It should explicitly set the
“taskmanager.memory.managed.size” to zero to check the potential
unexpected usage of off-heap memory.
> Introduce streaming task using heap backend e2e tests for Mesos
> ---------------------------------------------------------------
>
> Key: FLINK-15364
> URL: https://issues.apache.org/jira/browse/FLINK-15364
> Project: Flink
> Issue Type: Improvement
> Components: Tests
> Reporter: Yangze Guo
> Assignee: Yangze Guo
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> [As
> discussed|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Adding-e2e-tests-for-Flink-s-Mesos-integration-td35660.html],
> we need to test streaming task using heap backend. It should explicitly set
> the
> “taskmanager.memory.managed.size” to zero to check the potential
> unexpected usage of off-heap memory.
> This case tests whether Flink requests workers from Mesos with proper size
> and whether the dynamic properties are properly taking effect. This case also
> fills the gap of real interaction with Mesos.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
