[
https://issues.apache.org/jira/browse/FLINK-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237107#comment-17237107
]
Zhu Zhu commented on FLINK-20116:
---------------------------------
Test is done and no blocker issue is found.
{{Details:}}
Test jobs:
1. Streaming job with Rocksdb backend
2. Batch job with HashAgg operator which uses managed memory
3. Python job with python UDF
4. Streaming job with Rocksdb backend and python UDF
5. Batch job with Sort operator and and python UDF
Test cases:
1. Normal case: default value of "taskmanager.memory.managed.consumer-weights"
2. Normal case: consumer weights set to large values with a summation larger
than 100, e.g. "DATAPROC:200,PYTHON:100"
3. Exceptional case: required consumer weight set to zero, i.e.
"DATAPROC:30,PYTHON:0" or "DATAPROC:0,PYTHON:70"
4. Exceptional case: consumer weights all set to zero, i.e.
"DATAPROC:0,PYTHON:0"
Verification:
1. Is the feature working as expected under normal conditions
- status : Ok. Fractions are properly computed and used by batch operators,
RocksDB statebackends and Python UDF operator. Jobs successfully finished
2. Is the feature working / failing as expected with invalid input, induced
errors etc.
- status : almost Ok. Tasks fail due to invalid fraction when allocating
managed memory
- found FLINK-20284
3. Are the error messages, log messages, APIs etc. easy to understand
- opened FLINK-20282 FLINK-20283
4. Is the documentation easy to understand
- opened FLINK-20246
> Test Intra-Slot Managed Memory Sharing
> --------------------------------------
>
> Key: FLINK-20116
> URL: https://issues.apache.org/jira/browse/FLINK-20116
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Assignee: Zhu Zhu
> Priority: Critical
> Fix For: 1.12.0
>
>
> Introduced in https://issues.apache.org/jira/browse/FLINK-19177
> ----
> [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)
