[jira] [Commented] (YARN-3931) default-node-label-expression doesn’t apply when an application is submitted by RM rest api

[ https://issues.apache.org/jira/browse/YARN-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629489#comment-14629489 ] kyungwan nam commented on YARN-3931: node-label-expression is initialized to empty

[jira] [Created] (YARN-3931) default-node-label-expression doesn’t apply when an application is submitted by RM rest api

kyungwan nam created YARN-3931: -- Summary: default-node-label-expression doesn’t apply when an application is submitted by RM rest api Key: YARN-3931 URL: https://issues.apache.org/jira/browse/YARN-3931

[jira] [Commented] (YARN-3931) default-node-label-expression doesn’t apply when an application is submitted by RM rest api

[ https://issues.apache.org/jira/browse/YARN-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629701#comment-14629701 ] kyungwan nam commented on YARN-3931: hi, i couldn't reassign it to me. i think i don't

[jira] [Updated] (YARN-3931) default-node-label-expression doesn’t apply when an application is submitted by RM rest api

[ https://issues.apache.org/jira/browse/YARN-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-3931: --- Attachment: YARN-3931.001.patch I attached the patch. it work well in my cluster... :)

[jira] [Commented] (YARN-3931) default-node-label-expression doesn’t apply when an application is submitted by RM rest api

[ https://issues.apache.org/jira/browse/YARN-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634406#comment-14634406 ] kyungwan nam commented on YARN-3931: application-name, application-type” are empty

[jira] [Created] (YARN-4703) blacklist option for distributedshell

kyungwan nam created YARN-4703: -- Summary: blacklist option for distributedshell Key: YARN-4703 URL: https://issues.apache.org/jira/browse/YARN-4703 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-4703) blacklist option for distributedshell

[ https://issues.apache.org/jira/browse/YARN-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-4703: --- Attachment: YARN-4703.001.patch I attached a patch including test code. > blacklist option for

[jira] [Updated] (YARN-4703) blacklist option for distributedshell

[ https://issues.apache.org/jira/browse/YARN-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-4703: --- Attachment: YARN-4703.001.patch > blacklist option for distributedshell >

[jira] [Updated] (YARN-4703) blacklist option for distributedshell

[ https://issues.apache.org/jira/browse/YARN-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-4703: --- Attachment: (was: YARN-4703.001.patch) > blacklist option for distributedshell >

[jira] [Created] (YARN-6153) keepContainer does not work when AM retry window is set

kyungwan nam created YARN-6153: -- Summary: keepContainer does not work when AM retry window is set Key: YARN-6153 URL: https://issues.apache.org/jira/browse/YARN-6153 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153.001.patch if maybeLastAttempt in RMAppAttemptImpl is true, keepContainers is

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153.003.patch thanks for review. I'm uploading a new patch that is fixed as your

[jira] [Commented] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875688#comment-15875688 ] kyungwan nam commented on YARN-6153: {quote} In RMAppAttemptImpl, why is getStartTime used for checking

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153.005.patch my source tree was not up-to-date. that's why compile is failed. I'm

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153.004.patch thanks for review. yes, It looks better. I’m uploading a new patch. I

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153.002.patch thanks for your review. I'm attaching a new patch. - as your

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153.006.patch Thanks for your review. Ok. I'm uploading a new patch 006, which it

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153-branch-2.8.patch I'm uploading the patch for branch-2.8. 1. in the

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153.006-1.patch I'm uploading the additional patch for the hadoop-trunk.

[jira] [Commented] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892129#comment-15892129 ] kyungwan nam commented on YARN-6153: why I didn’t face the problem above 1 problem in the hadoop-trunk?

[jira] [Commented] (YARN-5696) add container_tag to Distributedshell's env

[ https://issues.apache.org/jira/browse/YARN-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15544076#comment-15544076 ] kyungwan nam commented on YARN-5696: for example, there are input directories /data/input/0,

[jira] [Created] (YARN-5696) add container_tag to Distributedshell's env

kyungwan nam created YARN-5696: -- Summary: add container_tag to Distributedshell's env Key: YARN-5696 URL: https://issues.apache.org/jira/browse/YARN-5696 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-5696) add container_tag to Distributedshell's env

[ https://issues.apache.org/jira/browse/YARN-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-5696: --- Attachment: YARN-5696-branch-2.7.3.001.patch > add container_tag to Distributedshell's env >

[jira] [Updated] (YARN-5696) add container_tag to Distributedshell's env

[ https://issues.apache.org/jira/browse/YARN-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-5696: --- Attachment: YARN-5696-branch-2.7.3.002.patch add num_containers env variable. following env variables

[jira] [Created] (YARN-5844) fair ordering policy with DRF

kyungwan nam created YARN-5844: -- Summary: fair ordering policy with DRF Key: YARN-5844 URL: https://issues.apache.org/jira/browse/YARN-5844 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-5844) fair ordering policy with DRF

[ https://issues.apache.org/jira/browse/YARN-5844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-5844: --- Attachment: YARN-5844.001.patch attached the patch. > fair ordering policy with DRF >

[jira] [Commented] (YARN-6401) terminating signal should be able to specify per application to support graceful-stop

[ https://issues.apache.org/jira/browse/YARN-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944787#comment-15944787 ] kyungwan nam commented on YARN-6401: thanks for your comment. signal is sent to the whole process

[jira] [Created] (YARN-6401) terminating signal should be able to specify per application to support graceful-stop

kyungwan nam created YARN-6401: -- Summary: terminating signal should be able to specify per application to support graceful-stop Key: YARN-6401 URL: https://issues.apache.org/jira/browse/YARN-6401

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: (was: YARN-6153.006-1.patch) > keepContainer does not work when AM retry window is set

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: (was: YARN-6153-branch-2.8.patch) > keepContainer does not work when AM retry window

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-6153: --- Attachment: YARN-6153-branch-2.8.patch Thanks for your comment... I'm uploading a new patch for the

[jira] [Updated] (YARN-3931) default-node-label-expression doesn’t apply when an application is submitted by RM rest api

[ https://issues.apache.org/jira/browse/YARN-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-3931: --- Attachment: YARN-3931.002.patch Sorry, I missed this issue for long time. I attached a patch including

[jira] [Updated] (YARN-7177) AvailableMB, AvailableVCores in the QueueMetrics is not correct when there are nodes whose node-label is not default

[ https://issues.apache.org/jira/browse/YARN-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-7177: --- Attachment: YARN-7177-branch-2.7.001.patch Attaches patch that queue statistics is calculated based on

[jira] [Commented] (YARN-7177) AvailableMB, AvailableVCores in the QueueMetrics is not correct when there are nodes whose node-label is not default

[ https://issues.apache.org/jira/browse/YARN-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158390#comment-16158390 ] kyungwan nam commented on YARN-7177: I have checked that absoluteUsedCapacity is not used in

[jira] [Created] (YARN-7177) AvailableMB, AvailableVCores in the QueueMetrics is not correct when there are nodes whose node-label is not default

kyungwan nam created YARN-7177: -- Summary: AvailableMB, AvailableVCores in the QueueMetrics is not correct when there are nodes whose node-label is not default Key: YARN-7177 URL:

[jira] [Created] (YARN-7352) inconsistent Node Label resources when NM who has running application is restarted with changed resource

kyungwan nam created YARN-7352: -- Summary: inconsistent Node Label resources when NM who has running application is restarted with changed resource Key: YARN-7352 URL: https://issues.apache.org/jira/browse/YARN-7352

[jira] [Commented] (YARN-7408) total capacity could be occupied by a large container request

[ https://issues.apache.org/jira/browse/YARN-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235682#comment-16235682 ] kyungwan nam commented on YARN-7408: Thanks to your comment, I was able to figure out that limiting

[jira] [Commented] (YARN-7408) total capacity could be occupied by a large container request

[ https://issues.apache.org/jira/browse/YARN-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224542#comment-16224542 ] kyungwan nam commented on YARN-7408: Hi [~jlowe]. Thank you for your comment and suggestion! I have a

[jira] [Updated] (YARN-8269) NPE happens when submit distributed shell with non-existing queue

[ https://issues.apache.org/jira/browse/YARN-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8269: --- Attachment: YARN-8269.001.patch > NPE happens when submit distributed shell with non-existing queue >

[jira] [Created] (YARN-8269) NPE happens when submit distributed shell with non-existing queue

kyungwan nam created YARN-8269: -- Summary: NPE happens when submit distributed shell with non-existing queue Key: YARN-8269 URL: https://issues.apache.org/jira/browse/YARN-8269 Project: Hadoop YARN

[jira] [Commented] (YARN-8269) NPE happens when submit distributed shell with non-existing queue

[ https://issues.apache.org/jira/browse/YARN-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470182#comment-16470182 ] kyungwan nam commented on YARN-8269: attaches a new patch with test code. please review it. thanks.

[jira] [Updated] (YARN-8269) NPE happens when submit distributed shell with non-existing queue

[ https://issues.apache.org/jira/browse/YARN-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8269: --- Attachment: YARN-8269.002.patch > NPE happens when submit distributed shell with non-existing queue >

[jira] [Created] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

kyungwan nam created YARN-8421: -- Summary: when moving app, activeUsers is increased, even though app does not have outstanding request Key: YARN-8421 URL: https://issues.apache.org/jira/browse/YARN-8421

[jira] [Updated] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

[jira] [Updated] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

[ https://issues.apache.org/jira/browse/YARN-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8421: --- Attachment: YARN-8421.002.patch > when moving app, activeUsers is increased, even though app does not

[jira] [Updated] (YARN-8179) Preemption does not happen due to natural_termination_factor when DRF is used

[ https://issues.apache.org/jira/browse/YARN-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8179: --- Attachment: YARN-8179.003.patch > Preemption does not happen due to natural_termination_factor when

[jira] [Commented] (YARN-8179) Preemption does not happen due to natural_termination_factor when DRF is used

[ https://issues.apache.org/jira/browse/YARN-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458432#comment-16458432 ] kyungwan nam commented on YARN-8179: Attached a new patch 003, which is based on up-to-date trunk. >

[jira] [Created] (YARN-7408) total capacity could be occupied by a large container request

kyungwan nam created YARN-7408: -- Summary: total capacity could be occupied by a large container request Key: YARN-7408 URL: https://issues.apache.org/jira/browse/YARN-7408 Project: Hadoop YARN

[jira] [Commented] (YARN-7408) total capacity could be occupied by a large container request

[ https://issues.apache.org/jira/browse/YARN-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221953#comment-16221953 ] kyungwan nam commented on YARN-7408: Currently, the number of reserved containers for an application is

[jira] [Updated] (YARN-8694) app flex with relative changes does not work

[ https://issues.apache.org/jira/browse/YARN-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8694: --- Attachment: YARN-8694.001.patch > app flex with relative changes does not work >

[jira] [Created] (YARN-8694) app flex with relative changes does not work

kyungwan nam created YARN-8694: -- Summary: app flex with relative changes does not work Key: YARN-8694 URL: https://issues.apache.org/jira/browse/YARN-8694 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593584#comment-16593584 ] kyungwan nam commented on YARN-8095: [~leftnoteasy], Sorry for bothering you. but could you share your

[jira] [Updated] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

[ https://issues.apache.org/jira/browse/YARN-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8421: --- Attachment: YARN-8421.003.patch > when moving app, activeUsers is increased, even though app does not

[jira] [Commented] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

[ https://issues.apache.org/jira/browse/YARN-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539625#comment-16539625 ] kyungwan nam commented on YARN-8421: [~eepayne], Thank you for your review. I've attached a new patch

[jira] [Commented] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

[ https://issues.apache.org/jira/browse/YARN-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542973#comment-16542973 ] kyungwan nam commented on YARN-8421: I've attached a patch for branch-2.8 Thanks [~eepayne], [~sunilg]

[jira] [Updated] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

[ https://issues.apache.org/jira/browse/YARN-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8421: --- Attachment: YARN-8421-branch-2.8.001.patch > when moving app, activeUsers is increased, even though

[jira] [Created] (YARN-8020) when DRF is used, preemption does not trigger due to incorrect idealAssigned

kyungwan nam created YARN-8020: -- Summary: when DRF is used, preemption does not trigger due to incorrect idealAssigned Key: YARN-8020 URL: https://issues.apache.org/jira/browse/YARN-8020 Project: Hadoop

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426751#comment-16426751 ] kyungwan nam commented on YARN-8095: Hi [~cheersyang] my configs are as follows. * ‘label1’ is set to

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433883#comment-16433883 ] kyungwan nam commented on YARN-8095: Hi. [~cheersyang] sorry for not clear explain. let’s consider

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435483#comment-16435483 ] kyungwan nam commented on YARN-8095: Hi [~cheersyang] Yes. that’d resolve the problem. besides, it

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429978#comment-16429978 ] kyungwan nam commented on YARN-8095: Hi. [~cheersyang] {quote}

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430190#comment-16430190 ] kyungwan nam commented on YARN-8095: I don't think that's a bug. an app with ‘label1’ node-label must

[jira] [Updated] (YARN-8179) Preemption does not happen due to natural_termination_factor when DRF is used

[ https://issues.apache.org/jira/browse/YARN-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8179: --- Attachment: YARN-8179.001.patch > Preemption does not happen due to natural_termination_factor when

[jira] [Created] (YARN-8179) Preemption does not happen due to natural_termination_factor when DRF is used

kyungwan nam created YARN-8179: -- Summary: Preemption does not happen due to natural_termination_factor when DRF is used Key: YARN-8179 URL: https://issues.apache.org/jira/browse/YARN-8179 Project:

[jira] [Commented] (YARN-8179) Preemption does not happen due to natural_termination_factor when DRF is used

[ https://issues.apache.org/jira/browse/YARN-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445532#comment-16445532 ] kyungwan nam commented on YARN-8179: Thanks [~eepayne], [~sunilg] for your comments. I'll work on new

[jira] [Commented] (YARN-8020) when DRF is used, preemption does not trigger due to incorrect idealAssigned

[ https://issues.apache.org/jira/browse/YARN-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445528#comment-16445528 ] kyungwan nam commented on YARN-8020: [~eepayne] I don’t think this is the same as YARN-8179. in case of

[jira] [Updated] (YARN-8179) Preemption does not happen due to natural_termination_factor when DRF is used

[ https://issues.apache.org/jira/browse/YARN-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8179: --- Attachment: YARN-8179.002.patch > Preemption does not happen due to natural_termination_factor when

[jira] [Commented] (YARN-8179) Preemption does not happen due to natural_termination_factor when DRF is used

[ https://issues.apache.org/jira/browse/YARN-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447705#comment-16447705 ] kyungwan nam commented on YARN-8179: Attached a patch with test case. and it will normalize up only if

[jira] [Updated] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8095: --- Attachment: YARN-8095-branch-2.8.001.patch > Allow disable non-exclusive allocation >

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440283#comment-16440283 ] kyungwan nam commented on YARN-8095: I attached a patch, which respect the accessible-node-lables even

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420266#comment-16420266 ] kyungwan nam commented on YARN-8095: any comment / suggestions are welcome > Allow disable

[jira] [Created] (YARN-8095) Allow disable non-exclusive allocation

kyungwan nam created YARN-8095: -- Summary: Allow disable non-exclusive allocation Key: YARN-8095 URL: https://issues.apache.org/jira/browse/YARN-8095 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-8095) Allow disable non-exclusive allocation

[ https://issues.apache.org/jira/browse/YARN-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421877#comment-16421877 ] kyungwan nam commented on YARN-8095: [~cheersyang] Thank you for your comment! If ‘longlived’ Queue is

[jira] [Commented] (YARN-8020) when DRF is used, preemption does not trigger due to incorrect idealAssigned

[ https://issues.apache.org/jira/browse/YARN-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405933#comment-16405933 ] kyungwan nam commented on YARN-8020: [~eepayne] Sorry for the late response. I've seen this problem

[jira] [Commented] (YARN-8020) when DRF is used, preemption does not trigger due to incorrect idealAssigned

[ https://issues.apache.org/jira/browse/YARN-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407717#comment-16407717 ] kyungwan nam commented on YARN-8020: I'm thinking the reason why it happens is as follows. {code:java}

[jira] [Updated] (YARN-8935) stopped yarn service app does not show when "yarn app -list"

[ https://issues.apache.org/jira/browse/YARN-8935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8935: --- Environment: (was: stopped yarn service app can be re-started or destroyed even if it does not

[jira] [Created] (YARN-8935) stopped yarn service app does not show when "yarn app -list"

kyungwan nam created YARN-8935: -- Summary: stopped yarn service app does not show when "yarn app -list" Key: YARN-8935 URL: https://issues.apache.org/jira/browse/YARN-8935 Project: Hadoop YARN

[jira] [Commented] (YARN-8694) app flex with relative changes does not work

[ https://issues.apache.org/jira/browse/YARN-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16664632#comment-16664632 ] kyungwan nam commented on YARN-8694: attaches a new patch 002. It will get the service status from api

[jira] [Updated] (YARN-8694) app flex with relative changes does not work

[ https://issues.apache.org/jira/browse/YARN-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8694: --- Attachment: YARN-8694.002.patch > app flex with relative changes does not work >

[jira] [Created] (YARN-9197) NPE in service AM when failed to launch container

kyungwan nam created YARN-9197: -- Summary: NPE in service AM when failed to launch container Key: YARN-9197 URL: https://issues.apache.org/jira/browse/YARN-9197 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-9197) NPE in service AM when failed to launch container

[ https://issues.apache.org/jira/browse/YARN-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-9197: --- Attachment: YARN-9197.001.patch > NPE in service AM when failed to launch container >

[jira] [Assigned] (YARN-9197) NPE in service AM when failed to launch container

[ https://issues.apache.org/jira/browse/YARN-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam reassigned YARN-9197: -- Assignee: kyungwan nam > NPE in service AM when failed to launch container >

[jira] [Created] (YARN-9243) Support limiting network outbound bandwidth for multiple interfaces

kyungwan nam created YARN-9243: -- Summary: Support limiting network outbound bandwidth for multiple interfaces Key: YARN-9243 URL: https://issues.apache.org/jira/browse/YARN-9243 Project: Hadoop YARN

[jira] [Commented] (YARN-9243) Support limiting network outbound bandwidth for multiple interfaces

[ https://issues.apache.org/jira/browse/YARN-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753756#comment-16753756 ] kyungwan nam commented on YARN-9243: Attaches patch. please review or any comment > Support limiting

[jira] [Assigned] (YARN-9243) Support limiting network outbound bandwidth for multiple interfaces

[ https://issues.apache.org/jira/browse/YARN-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam reassigned YARN-9243: -- Assignee: kyungwan nam > Support limiting network outbound bandwidth for multiple interfaces >

[jira] [Updated] (YARN-9243) Support limiting network outbound bandwidth for multiple interfaces

[ https://issues.apache.org/jira/browse/YARN-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-9243: --- Attachment: YARN-9243.001.patch > Support limiting network outbound bandwidth for multiple interfaces

[jira] [Created] (YARN-9386) destroying yarn-service is allowed even though running state

kyungwan nam created YARN-9386: -- Summary: destroying yarn-service is allowed even though running state Key: YARN-9386 URL: https://issues.apache.org/jira/browse/YARN-9386 Project: Hadoop YARN

[jira] [Commented] (YARN-9386) destroying yarn-service is allowed even though running state

[ https://issues.apache.org/jira/browse/YARN-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792743#comment-16792743 ] kyungwan nam commented on YARN-9386: attaches a patch. prior to delete service, it would check whether

[jira] [Updated] (YARN-9386) destroying yarn-service is allowed even though running state

[ https://issues.apache.org/jira/browse/YARN-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-9386: --- Attachment: YARN-9386.001.patch > destroying yarn-service is allowed even though running state >

[jira] [Commented] (YARN-9386) destroying yarn-service is allowed even though running state

[ https://issues.apache.org/jira/browse/YARN-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798650#comment-16798650 ] kyungwan nam commented on YARN-9386: attaches a new patch, which fixes test code. > destroying

[jira] [Updated] (YARN-9386) destroying yarn-service is allowed even though running state

[ https://issues.apache.org/jira/browse/YARN-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-9386: --- Attachment: YARN-9386.002.patch > destroying yarn-service is allowed even though running state >

[jira] [Created] (YARN-9307) node_partitions constraint does not work

kyungwan nam created YARN-9307: -- Summary: node_partitions constraint does not work Key: YARN-9307 URL: https://issues.apache.org/jira/browse/YARN-9307 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-9307) node_partitions constraint does not work

[ https://issues.apache.org/jira/browse/YARN-9307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-9307: --- Attachment: YARN-9307.branch-3.1.001.patch > node_partitions constraint does not work >

[jira] [Commented] (YARN-9307) node_partitions constraint does not work

[ https://issues.apache.org/jira/browse/YARN-9307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768856#comment-16768856 ] kyungwan nam commented on YARN-9307: I attached a patch for hadoop-3.1. It seems this is fixed in

[jira] [Updated] (YARN-9386) destroying yarn-service is allowed even though running state

[ https://issues.apache.org/jira/browse/YARN-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-9386: --- Attachment: YARN-9386.003.patch > destroying yarn-service is allowed even though running state >

[jira] [Commented] (YARN-9386) destroying yarn-service is allowed even though running state

[ https://issues.apache.org/jira/browse/YARN-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856300#comment-16856300 ] kyungwan nam commented on YARN-9386: [~billie.rinaldi], I've attached a new patch including your

[jira] [Commented] (YARN-9386) destroying yarn-service is allowed even though running state

[ https://issues.apache.org/jira/browse/YARN-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852719#comment-16852719 ] kyungwan nam commented on YARN-9386: Thank you for your comment! [~billie.rinaldi] I agreed with you.

[jira] [Commented] (YARN-9521) RM failed to start due to system services

[ https://issues.apache.org/jira/browse/YARN-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868310#comment-16868310 ] kyungwan nam commented on YARN-9521: {code:java} 2019-06-18 18:47:38,634 INFO

[jira] [Commented] (YARN-9521) RM filed to start due to system services

[ https://issues.apache.org/jira/browse/YARN-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840096#comment-16840096 ] kyungwan nam commented on YARN-9521: I think the cause of this problem is as follows. 1. _fs_ is set

[jira] [Commented] (YARN-9521) RM filed to start due to system services

[ https://issues.apache.org/jira/browse/YARN-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845571#comment-16845571 ] kyungwan nam commented on YARN-9521: Please let me know if anyone has any ideas on how to resolve.

  1   2   >