[
https://issues.apache.org/jira/browse/FLINK-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger updated FLINK-20125:
-----------------------------------
Description:
The following questions should be answered for the different deployment modes
(application cluster, per-Job cluster, session cluster) and deployment backends
(Standalone/Local, Kubernetes, Yarn, Mesos):
- Does the TaskManager metrics page (path:
/#/task-manager/<taskmanager-id>/metrics) looks as proposed in FLIP-102 (minor
improvements where introduced in )? It helps to have a job running to see
whether the metrics in the right column are actually dynamically changing.
- Check whether all 8 newly introduced metrics are exposed through the
TaskManager's metric endpoint:
- Does the JobManager metrics page (path: /#/job-manager/metrics) as proposed
in FLIP-104?
- Does the Cluster configuration endpoint include /#/job-manager/config include
memory-related parameters like jobmanager.memory.heap.size,
jobmanager.memory.jvm-metaspace.size, or jobmanager.memory.off-heap.size? Do
they match configuration parameters possibly set in the config file?
Improved unaligned checkpointing times under backpressure
(See wiki for more details!)
----
[General Information about the Flink 1.12 release
testing|https://cwiki.apache.org/confluence/display/FLINK/1.12+Release+-+Community+Testing]
When testing a feature, consider the following aspects:
- Is the documentation easy to understand
- Are the error messages, log messages, APIs etc. easy to understand
- Is the feature working as expected under normal conditions
- Is the feature working / failing as expected with invalid input, induced
errors etc.
If you find a problem during testing, please file a ticket (Priority=Critical;
Fix Version = 1.12.0), and link it in this testing ticket.
During the testing keep us updated on tests conducted, or please write a short
summary of all things you have tested in the end.
was:
----
[General Information about the Flink 1.12 release
testing|https://cwiki.apache.org/confluence/display/FLINK/1.12+Release+-+Community+Testing]
When testing a feature, consider the following aspects:
- Is the documentation easy to understand
- Are the error messages, log messages, APIs etc. easy to understand
- Is the feature working as expected under normal conditions
- Is the feature working / failing as expected with invalid input, induced
errors etc.
If you find a problem during testing, please file a ticket (Priority=Critical;
Fix Version = 1.12.0), and link it in this testing ticket.
During the testing keep us updated on tests conducted, or please write a short
summary of all things you have tested in the end.
> Test memory configuration display in the web ui
> -----------------------------------------------
>
> Key: FLINK-20125
> URL: https://issues.apache.org/jira/browse/FLINK-20125
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Assignee: Xintong Song
> Priority: Critical
> Fix For: 1.12.0
>
>
> The following questions should be answered for the different deployment modes
> (application cluster, per-Job cluster, session cluster) and deployment
> backends (Standalone/Local, Kubernetes, Yarn, Mesos):
> - Does the TaskManager metrics page (path:
> /#/task-manager/<taskmanager-id>/metrics) looks as proposed in FLIP-102
> (minor improvements where introduced in )? It helps to have a job running to
> see whether the metrics in the right column are actually dynamically changing.
> - Check whether all 8 newly introduced metrics are exposed through the
> TaskManager's metric endpoint:
> - Does the JobManager metrics page (path: /#/job-manager/metrics) as proposed
> in FLIP-104?
> - Does the Cluster configuration endpoint include /#/job-manager/config
> include memory-related parameters like jobmanager.memory.heap.size,
> jobmanager.memory.jvm-metaspace.size, or jobmanager.memory.off-heap.size? Do
> they match configuration parameters possibly set in the config file?
> Improved unaligned checkpointing times under backpressure
> (See wiki for more details!)
> ----
> [General Information about the Flink 1.12 release
> testing|https://cwiki.apache.org/confluence/display/FLINK/1.12+Release+-+Community+Testing]
> When testing a feature, consider the following aspects:
> - Is the documentation easy to understand
> - Are the error messages, log messages, APIs etc. easy to understand
> - Is the feature working as expected under normal conditions
> - Is the feature working / failing as expected with invalid input, induced
> errors etc.
> If you find a problem during testing, please file a ticket
> (Priority=Critical; Fix Version = 1.12.0), and link it in this testing ticket.
> During the testing keep us updated on tests conducted, or please write a
> short summary of all things you have tested in the end.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
