-
Notifications
You must be signed in to change notification settings - Fork 13.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FLINK-15198][Deployment / Mesos] remove mesos.resourcemanager.tasks.mem #10890
[FLINK-15198][Deployment / Mesos] remove mesos.resourcemanager.tasks.mem #10890
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit 1587714 (Fri Feb 28 21:49:11 UTC 2020) ✅no warnings Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution @PengTaoWW . However, I think you could not just change the key to the MESOS_RM_TASKS_MEMORY_MB
. You need to provide another solution.
@@ -64,7 +64,7 @@ | |||
*/ | |||
@Deprecated | |||
public static final ConfigOption<Integer> MESOS_RM_TASKS_MEMORY_MB = | |||
key("mesos.resourcemanager.tasks.mem") | |||
key("taskmanager.memory.total-process.size") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could not simply change the key.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from https://github.com/apache/flink/pull/10513/files#r356585015, just need to delete the code and comments that use MEMOS_RM_TASKS_MEMORY_MB?
@KarmaGYZ I modified the code and deleted the part that used 'mesos.resourcemanager.tasks.mem' in the code。 |
@flinkbot run travis |
flink-jepsen/src/jepsen/flink/db.clj
Outdated
@@ -303,7 +303,7 @@ | |||
"-Djobmanager.rpc.address=$(hostname -f)" | |||
"-Djobmanager.rpc.port=6123" | |||
"-Dmesos.resourcemanager.tasks.cpus=1" | |||
"-Dmesos.resourcemanager.tasks.mem=2048" ;; FLINK-15082: this option must be set instead of taskmanager.memory.process.size | |||
"-Dtaskmanager.memory.process.size=2048m" ;; FLINK-15082: this option must be set instead of taskmanager.memory.process.size |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this note could be removed after this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me fix it
if (configuration.contains(MESOS_RM_TASKS_MEMORY_MB) && | ||
configuration.contains(TaskManagerOptions.TOTAL_PROCESS_MEMORY) && | ||
!legacyTotalProcessMemory.equals(unifiedTotalProcessMemory)) { | ||
if (!configuration.contains(TaskManagerOptions.TOTAL_PROCESS_MEMORY)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure that the total process memory should be explicitly set here. According to the FLIP-49 Doc. User need either of these three options configured:
- Task Heap Memory and Managed Memory
- Total Flink Memory
- Total Process Memory
After this PR, I think we could directly construct the TaskExecutorResourceSpec from the flinkConfig. @azagrebin Please correct me if I have any misunderstanding.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, we do not need this method getTotalProcessMemory
anymore.
TaskExecutorProcessUtils
will parse the options in createContaineredTaskManagerParameters
.
Subsequently, we do not need .withTotalProcessMemory(totalProcessMemory)
in createContaineredTaskManagerParameters
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will remove .withTotalProcessMemory (totalProcessMemory) in createContaineredTaskManagerParameters and delete the getTotalProcessMemory method
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@azagrebin Already modified
fbce565
to
0ec632d
Compare
@flinkbot run travis |
1 similar comment
@flinkbot run travis |
f683466
to
7c3dadd
Compare
@PengTaoWW |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if (configuration.contains(MESOS_RM_TASKS_MEMORY_MB) && | ||
configuration.contains(TaskManagerOptions.TOTAL_PROCESS_MEMORY) && | ||
!legacyTotalProcessMemory.equals(unifiedTotalProcessMemory)) { | ||
if (!configuration.contains(TaskManagerOptions.TOTAL_PROCESS_MEMORY)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, we do not need this method getTotalProcessMemory
anymore.
TaskExecutorProcessUtils
will parse the options in createContaineredTaskManagerParameters
.
Subsequently, we do not need .withTotalProcessMemory(totalProcessMemory)
in createContaineredTaskManagerParameters
.
@flinkbot run travis |
fix https://issues.apache.org/jira/projects/FLINK/issues/FLINK-15198 Delete getTotalProcessMemory remove .withTotalProcessMemory (totalProcessMemory) in createContaineredTaskManagerParameters and delete the getTotalProcessMemory method
1c28ae3
to
f5282a9
Compare
@flinkbot run travis |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing the comments @PengTaoWW , LGTM
I also pushed a small migration doc fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update. @PengTaoWW . It generally LGTM. Just two minor comments.
@@ -134,7 +134,7 @@ but they still have the same semantics for the job manager process. See also [ho | |||
The previous options which were responsible for the total memory used by Flink are `taskmanager.heap.size` or `taskmanager.heap.mb`. | |||
Despite their naming, they included not only JVM heap but also other off-heap memory components. The options have been deprecated. | |||
|
|||
The Mesos integration also had a separate option with the same semantics: `mesos.resourcemanager.tasks.mem` which has also been deprecated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just remove this line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it is a migration guide from Flink <= 1.9, the option always was in Flink <= 1.9, so I think it is still worth mentioning it here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. +1 to merge this PR.
@@ -134,7 +134,7 @@ but they still have the same semantics for the job manager process. See also [ho | |||
The previous options which were responsible for the total memory used by Flink are `taskmanager.heap.size` or `taskmanager.heap.mb`. | |||
Despite their naming, they included not only JVM heap but also other off-heap memory components. The options have been deprecated. | |||
|
|||
The Mesos integration also had a separate option with the same semantics: `mesos.resourcemanager.tasks.mem` which has also been deprecated. | |||
The Mesos integration also had a separate option with the same semantics: `mesos.resourcemanager.tasks.mem` which has also been removed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto.
Thank you for your help, I will continue to contribute |
fix https://issues.apache.org/jira/projects/FLINK/issues/FLINK-15198
What is the purpose of the change
In FLINK-15082, we deprecated 'mesos.resourcemanager.tasks.mem' in favour of the new unified option 'taskmanager.memory.total-process.size' from FLIP-49. We should remove it now in 1.11.
https://issues.apache.org/jira/projects/FLINK/issues/FLINK-15198?filter=allopenissues
Brief change log
modified the code and deleted the part that used 'mesos.resourcemanager.tasks.mem' in the code
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
Documentation