[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324560#comment-15324560 ] MENG DING commented on YARN-5221: - Hi, [~leftnoteasy] I have not been following this for a while, but it

[jira] [Updated] (YARN-4671) There is no need to acquire CS lock when completing a container

[ https://issues.apache.org/jira/browse/YARN-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4671: Attachment: YARN-4671.2.patch Rebased against trunk > There is no need to acquire CS lock when completing a

[jira] [Updated] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4138: Attachment: YARN-4138.7.patch Fix the failed unit test case

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15137639#comment-15137639 ] MENG DING commented on YARN-4138: - The checkstyle warnings are not fixable. The failed tests are not

[jira] [Updated] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4138: Attachment: YARN-4138.6.patch Attaching a new patch that updates {{lastConfirmedResource}} based on NM

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134878#comment-15134878 ] MENG DING commented on YARN-4138: - The difference between the two allocationExpirationInfo is that the

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15134926#comment-15134926 ] MENG DING commented on YARN-4138: - Hi, [~jianhe] and [~sandflee] After more thoughts, I think we should be

[jira] [Created] (YARN-4671) There is no need to acquire CS lock when completing a container

MENG DING created YARN-4671: --- Summary: There is no need to acquire CS lock when completing a container Key: YARN-4671 URL: https://issues.apache.org/jira/browse/YARN-4671 Project: Hadoop YARN

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15132466#comment-15132466 ] MENG DING commented on YARN-4138: - Hi, [~jianhe] I think with a bit of explanation this won't cause

[jira] [Updated] (YARN-4671) There is no need to acquire CS lock when completing a container

[ https://issues.apache.org/jira/browse/YARN-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4671: Description: In YARN-4519, we discovered that there is no need to acquire CS lock in

[jira] [Updated] (YARN-4671) There is no need to acquire CS lock when completing a container

[ https://issues.apache.org/jira/browse/YARN-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4671: Attachment: YARN-4671.1.patch Attaching the initial patch for review. * I need to make

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131201#comment-15131201 ] MENG DING commented on YARN-4138: - The failed tests are not related. > Roll back container resource

[jira] [Updated] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4138: Attachment: YARN-4138.5.patch Hi, [~jianhe] bq. After step 6, rmContainer.getLastConfirmedResource() will

[jira] [Updated] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4138: Attachment: YARN-4138.4.patch Attaching new patch now that YARN-4519 is completed. In

[jira] [Commented] (YARN-4599) Set OOM control for memory cgroups

[ https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129300#comment-15129300 ] MENG DING commented on YARN-4599: - I have a question regarding when OOM controller will kick in. Is it true

[jira] [Commented] (YARN-4599) Set OOM control for memory cgroups

[ https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129309#comment-15129309 ] MENG DING commented on YARN-4599: - [~aw]: bq. We need this as something that can be set and I'd propose

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121857#comment-15121857 ] MENG DING commented on YARN-4519: - Thanks [~leftnoteasy]. I will log a separate ticket for

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15117468#comment-15117468 ] MENG DING commented on YARN-4519: - Hi, [~leftnoteasy] bq. IIUC, after this patch, increase/decrease

[jira] [Updated] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4519: Attachment: YARN-4519.3.patch [~jianhe] and I had a discussion offline. Instead of grabbing the CS lock for

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098974#comment-15098974 ] MENG DING commented on YARN-4108: - Hi, [~leftnoteasy], will there be a separate ticket to track the issue

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092054#comment-15092054 ] MENG DING commented on YARN-4519: - The JavaDoc and unit tests error are not related to this issue. >

[jira] [Updated] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4519: Attachment: YARN-4519.2.patch Attaching new patch that addressed the failed test case. We only need to

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15088361#comment-15088361 ] MENG DING commented on YARN-4519: - Please ignore the previous patch. I think there is way for improvement.

[jira] [Updated] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4519: Attachment: YARN-4519.1.patch Attaching the latest patch that addresses this issue: bq. We need to make

[jira] [Commented] (YARN-4528) decreaseContainer Message maybe lost if NM restart

[ https://issues.apache.org/jira/browse/YARN-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081550#comment-15081550 ] MENG DING commented on YARN-4528: - Hi, [~sandflee] With current logic, I think RM won't know if a

[jira] [Commented] (YARN-4528) decreaseContainer Message maybe lost if NM restart

[ https://issues.apache.org/jira/browse/YARN-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082083#comment-15082083 ] MENG DING commented on YARN-4528: - Honestly I don't think the design needs to be changed, unless other

[jira] [Commented] (YARN-4528) decreaseContainer Message maybe lost if NM restart

[ https://issues.apache.org/jira/browse/YARN-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081267#comment-15081267 ] MENG DING commented on YARN-4528: - Hi, [~sandflee] I am not quite sure about the benefit of directly

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074082#comment-15074082 ] MENG DING commented on YARN-4495: - I guess my point is if you are not going to do any automated action upon

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073991#comment-15073991 ] MENG DING commented on YARN-4519: - Hi, [~sandflee] The delta resource is the difference between currently

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074028#comment-15074028 ] MENG DING commented on YARN-4495: - Hi, [~sandflee] What is your specific use case? Do you plan to catch

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073355#comment-15073355 ] MENG DING commented on YARN-4495: - Hi, [~sandflee] I was just thinking would it be simpler to modify the

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072873#comment-15072873 ] MENG DING commented on YARN-4519: - I feel that the correct solution would be simply put all decrease

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072880#comment-15072880 ] MENG DING commented on YARN-4138: - Hi, [~sandflee] I think this issue depends on YARN-4519. Will suspend

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073067#comment-15073067 ] MENG DING commented on YARN-4519: - This approach would be simpler, at the expense of acquiring a CS lock in

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073316#comment-15073316 ] MENG DING commented on YARN-4519: - Yes the race only happens when computing delta resource, and yes it also

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073321#comment-15073321 ] MENG DING commented on YARN-4519: - Agreed :-) > potential deadlock of CapacityScheduler between decrease

[jira] [Assigned] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING reassigned YARN-4519: --- Assignee: MENG DING > potential deadlock of CapacityScheduler between decrease container and assign

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072426#comment-15072426 ] MENG DING commented on YARN-4138: - Release containers may have the same issue too. Strange that there has

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072480#comment-15072480 ] MENG DING commented on YARN-4138: - You are right, I remembered that wrong. > Roll back container resource

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071682#comment-15071682 ] MENG DING commented on YARN-4138: - Hi, [~sandflee] In your step 3, the container will NOT be removed from

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071684#comment-15071684 ] MENG DING commented on YARN-4138: - Hi, [~sandflee] Can you provide a test case if you believe there is a

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071080#comment-15071080 ] MENG DING commented on YARN-4138: - Hi, [~jianhe] I just tried to apply the patch on the latest trunk, and

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15070534#comment-15070534 ] MENG DING commented on YARN-4138: - Hi [~jianhe], which file(s) are you referring to in particular? > Roll

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064134#comment-15064134 ] MENG DING commented on YARN-4138: - Hi, [~sandflee] 1. Yes, this is the expected behavior. If you take a

[jira] [Updated] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4138: Attachment: YARN-4138.3.patch Attach latest patch that addresses [~jianhe] and [~sandflee]'s comments. I

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063066#comment-15063066 ] MENG DING commented on YARN-4138: - Hi, [~jianhe] Thanks for reviewing the code. * I think you are right

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15063209#comment-15063209 ] MENG DING commented on YARN-4138: - Thanks [~sandflee] for the review. bq. use

[jira] [Commented] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061393#comment-15061393 ] MENG DING commented on YARN-1197: - [~sandflee], for now you can achieve the goal of increasing and

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15056056#comment-15056056 ] MENG DING commented on YARN-4138: - Hi, [~sandflee] The proposed implementation of the token expiration and

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052890#comment-15052890 ] MENG DING commented on YARN-4138: - Hi, [~sandflee] Not sure if I fully understand your question. If

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14989637#comment-14989637 ] MENG DING commented on YARN-1510: - I just ran these tests locally with latest trunk and YARN-1510 applied,

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14989648#comment-14989648 ] MENG DING commented on YARN-1510: - Also ran the following tests, they passed: {code}

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14987876#comment-14987876 ] MENG DING commented on YARN-1510: - The mvn install test is flawed. It goes directly into

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14987868#comment-14987868 ] MENG DING commented on YARN-1509: - The test failure should be related to YARN-4326. In addition, the mvn

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14988091#comment-14988091 ] MENG DING commented on YARN-1510: - I logged YETUS-159 for this issue. > Make NMClient support change

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14987966#comment-14987966 ] MENG DING commented on YARN-1510: - [~leftnoteasy], should I log this in the Apache Yetus community? > Make

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.9.patch Thanks [~jianhe] for reviewing the patch and giving feedback offline. To

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.10.patch Please ignore the previous patch, and see the latest one. > Make AMRMClient

[jira] [Updated] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1510: Attachment: YARN-1510.7.patch Thank you so much for catching this, [~jianhe]! Attaching latest patch that

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986162#comment-14986162 ] MENG DING commented on YARN-1510: - The mvninstall error and failed tests should not be related to this

[jira] [Created] (YARN-4326) TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188

MENG DING created YARN-4326: --- Summary: TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188 Key: YARN-4326 URL: https://issues.apache.org/jira/browse/YARN-4326

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986336#comment-14986336 ] MENG DING commented on YARN-1510: - Logged YARN-4326 for the TestDistributedShell timeout issue. > Make

[jira] [Updated] (YARN-4326) TestDistributedShell timeout as AHS in MiniYarnCluster no longer binds to default port 8188

[ https://issues.apache.org/jira/browse/YARN-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4326: Attachment: YARN-4326.patch Fix the problem by setting the {{TIMELINE_SERVICE_WEBAPP_ADDRESS}} after

[jira] [Commented] (YARN-4287) Capacity Scheduler: Rack Locality improvement

[ https://issues.apache.org/jira/browse/YARN-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980886#comment-14980886 ] MENG DING commented on YARN-4287: - Looking at this issue, I have to admit that I had been frustrated with

[jira] [Commented] (YARN-4287) Capacity Scheduler: Rack Locality improvement

[ https://issues.apache.org/jira/browse/YARN-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981232#comment-14981232 ] MENG DING commented on YARN-4287: - Agreed. > Capacity Scheduler: Rack Locality improvement >

[jira] [Commented] (YARN-4175) Example of use YARN-1197

[ https://issues.apache.org/jira/browse/YARN-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978444#comment-14978444 ] MENG DING commented on YARN-4175: - Correct a typo in the previous post. It should be {{app_id}} instead of

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978430#comment-14978430 ] MENG DING commented on YARN-1509: - The failed tests are not related. > Make AMRMClient support send

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.8.patch Thanks [~leftnoteasy] for the comments. Your concern is valid. I have updated

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.7.patch Update the patch to include comments on deprecated interface/methods to refer

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975294#comment-14975294 ] MENG DING commented on YARN-1510: - Failed tests are not related. > Make NMClient support change container

[jira] [Updated] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1510: Attachment: YARN-1510.6.patch Added comments to refer to the new class/methods for the deprecated interface

[jira] [Updated] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1510: Attachment: YARN-1510.5.patch Attaching latest patch that deprecated the {{NMClientAsync.CallbackHandler}}.

[jira] [Updated] (YARN-4175) Example of use YARN-1197

[ https://issues.apache.org/jira/browse/YARN-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4175: Attachment: YARN-4175.2.patch Update the example program as client APIs have been changed in YARN-1509 and

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960927#comment-14960927 ] MENG DING commented on YARN-1509: - Hi, [~bikassaha] Thanks for the comments. I probably didn't make

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.6.patch Attaching new patch that address the following issues: * Combine

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959077#comment-14959077 ] MENG DING commented on YARN-1509: - Hi, [~bikassaha] Apologize for the late response, I was out traveling

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14959502#comment-14959502 ] MENG DING commented on YARN-1509: - bq. I didn't find existing tests that test the pending list on RM

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948709#comment-14948709 ] MENG DING commented on YARN-1509: - Hi, [~bikassaha] Thanks a lot for the valuable comments! bq. Why are

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14949639#comment-14949639 ] MENG DING commented on YARN-1509: - Had an offline discussion with [~leftnoteasy] and [~bikassaha]. Overall

[jira] [Commented] (YARN-3026) Move application-specific container allocation logic from LeafQueue to FiCaSchedulerApp

[ https://issues.apache.org/jira/browse/YARN-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947680#comment-14947680 ] MENG DING commented on YARN-3026: - Hi, [~leftnoteasy] I've got another question while studying this patch.

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.5.patch Thanks [~leftnoteasy]. Attaching the patch that addresses the comments. >

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14947056#comment-14947056 ] MENG DING commented on YARN-1509: - Test failure is not related to this patch. Checkstyle warning is the

[jira] [Commented] (YARN-4175) Example of use YARN-1197

[ https://issues.apache.org/jira/browse/YARN-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945988#comment-14945988 ] MENG DING commented on YARN-4175: - Update on my testing result. Based on my tests of this feature against

[jira] [Updated] (YARN-4230) Increasing container resource while there is no headroom left will cause ResourceManager to crash

[ https://issues.apache.org/jira/browse/YARN-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4230: Attachment: YARN-4230.1.patch The fix is simple. Attaching the patch with an added test case. > Increasing

[jira] [Created] (YARN-4230) Increasing container resource while there is no headroom left will cause ResourceManager to crash

MENG DING created YARN-4230: --- Summary: Increasing container resource while there is no headroom left will cause ResourceManager to crash Key: YARN-4230 URL: https://issues.apache.org/jira/browse/YARN-4230

[jira] [Commented] (YARN-4175) Example of use YARN-1197

[ https://issues.apache.org/jira/browse/YARN-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944039#comment-14944039 ] MENG DING commented on YARN-4175: - I am using the example application to test the container

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.4.patch Submit the new patch that fixes the whitespace issue > Make AMRMClient

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943406#comment-14943406 ] MENG DING commented on YARN-1510: - * The release audit is not related. * The failed test passed in my own

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943587#comment-14943587 ] MENG DING commented on YARN-1509: - * release audit is not related * will apply for exception for

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.3.patch Attaching latest patch: * Added AbstractCallbackHandler in AMRMClientAsync *

[jira] [Updated] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1510: Attachment: YARN-1510.4.patch Attach latest patch which adds an {{NMClientAsync.AbstractCallbackHandler}}

[jira] [Updated] (YARN-4175) Example of use YARN-1197

[ https://issues.apache.org/jira/browse/YARN-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4175: Attachment: YARN-4175.1.patch Submit the initial patch for review. Will not kick jenkins as it depends on

[jira] [Commented] (YARN-4175) Example of use YARN-1197

[ https://issues.apache.org/jira/browse/YARN-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14938919#comment-14938919 ] MENG DING commented on YARN-4175: - Update on the progress of this ticket: The example will be based on the

[jira] [Commented] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14935681#comment-14935681 ] MENG DING commented on YARN-1509: - Thanks for the review [~leftnoteasy]! bq. I think we can simply add

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.2.patch > Make AMRMClient support send increase container request and get >

[jira] [Updated] (YARN-1509) Make AMRMClient support send increase container request and get increased/decreased containers

[ https://issues.apache.org/jira/browse/YARN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1509: Attachment: YARN-1509.1.patch Submit the first patch for review. [~leftnoteasy], recall during design stage

[jira] [Commented] (YARN-4175) Example of use YARN-1197

[ https://issues.apache.org/jira/browse/YARN-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908669#comment-14908669 ] MENG DING commented on YARN-4175: - Hi, [~leftnoteasy], if you are not working on this right now, I will be

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908436#comment-14908436 ] MENG DING commented on YARN-1510: - I forgot to say that the failed tests are not related, as they all

[jira] [Commented] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14908456#comment-14908456 ] MENG DING commented on YARN-1510: - One thing I want to bring up for discussion is that this ticket adds two

[jira] [Updated] (YARN-1510) Make NMClient support change container resources

[ https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1510: Attachment: YARN-1510.3.patch YARN-1197 has been merged into trunk. Attaching new patch based on trunk. >

  1   2   3   >