[jira] [Commented] (YARN-5829) FS preemption should reserve a node before considering containers on it for preemption

[ https://issues.apache.org/jira/browse/YARN-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904453#comment-15904453 ] Miklos Szegedi commented on YARN-5829: -- [~Tao Jie], I like the idea that you described in YARN-5636.

[jira] [Created] (YARN-6302) Fail the node, if Linux Container Executor is not configured properly

Miklos Szegedi created YARN-6302: Summary: Fail the node, if Linux Container Executor is not configured properly Key: YARN-6302 URL: https://issues.apache.org/jira/browse/YARN-6302 Project: Hadoop

[jira] [Commented] (YARN-6218) TestAMRMClient fails with fair scheduler

[ https://issues.apache.org/jira/browse/YARN-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892763#comment-15892763 ] Miklos Szegedi commented on YARN-6218: -- Thank you, [~yufeigu] for the comments, I updated the patch.

[jira] [Updated] (YARN-6218) TestAMRMClient fails with fair scheduler

[ https://issues.apache.org/jira/browse/YARN-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6218: - Attachment: YARN-6218.002.patch > TestAMRMClient fails with fair scheduler >

[jira] [Commented] (YARN-6249) TestFairSchedulerPreemption is inconsistently failing on trunk

[ https://issues.apache.org/jira/browse/YARN-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892705#comment-15892705 ] Miklos Szegedi commented on YARN-6249: -- Thank you, [~Tao Jie] for the debugging and the patch. It

[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=15889309#comment-15889309 ] Miklos Szegedi commented on YARN-4599: -- Thank you for the patch [~sandflee]. This would be useful for

[jira] [Commented] (YARN-6172) TestFSAppStarvation fails on trunk

[ https://issues.apache.org/jira/browse/YARN-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884845#comment-15884845 ] Miklos Szegedi commented on YARN-6172: -- Thank you, [~kasha] for the comments. I updated the patch.

[jira] [Updated] (YARN-6172) TestFSAppStarvation fails on trunk

[ https://issues.apache.org/jira/browse/YARN-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6172: - Attachment: YARN-6172.001.patch > TestFSAppStarvation fails on trunk >

[jira] [Commented] (YARN-6231) TestFairScheduler::testMoveWouldViolateMaxResourcesConstraints failing on branch-2

[ https://issues.apache.org/jira/browse/YARN-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884833#comment-15884833 ] Miklos Szegedi commented on YARN-6231: -- [~kasha], is this the same issue as YARN-6230? >

[jira] [Commented] (YARN-5548) Use MockRMMemoryStateStore to reduce test failures

[ https://issues.apache.org/jira/browse/YARN-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883645#comment-15883645 ] Miklos Szegedi commented on YARN-5548: -- Thank you, [~bibinchundatt] for the patch. I see this pretty

[jira] [Created] (YARN-6230) Failing unit test TestFairScheduler.testMoveWouldViolateMaxResourcesConstraints

Miklos Szegedi created YARN-6230: Summary: Failing unit test TestFairScheduler.testMoveWouldViolateMaxResourcesConstraints Key: YARN-6230 URL: https://issues.apache.org/jira/browse/YARN-6230 Project:

[jira] [Updated] (YARN-6218) TestAMRMClient fails with fair scheduler

[ https://issues.apache.org/jira/browse/YARN-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6218: - Attachment: YARN-6218.001.patch Thank you, [~haibochen] for the review. I updated the patch. >

[jira] [Assigned] (YARN-6172) TestFSAppStarvation fails on trunk

[ https://issues.apache.org/jira/browse/YARN-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi reassigned YARN-6172: Assignee: Miklos Szegedi > TestFSAppStarvation fails on trunk >

[jira] [Updated] (YARN-6172) TestFSAppStarvation fails on trunk

[ https://issues.apache.org/jira/browse/YARN-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6172: - Attachment: YARN-6172.000.patch > TestFSAppStarvation fails on trunk >

[jira] [Comment Edited] (YARN-6172) TestFSAppStarvation fails on trunk

[ https://issues.apache.org/jira/browse/YARN-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881712#comment-15881712 ] Miklos Szegedi edited comment on YARN-6172 at 2/24/17 1:23 AM: --- Thank you,

[jira] [Commented] (YARN-6172) TestFSAppStarvation fails on trunk

[ https://issues.apache.org/jira/browse/YARN-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881712#comment-15881712 ] Miklos Szegedi commented on YARN-6172: -- I was able to repro the scenario above. There are two issues

[jira] [Commented] (YARN-6218) TestAMRMClient fails with fair scheduler

[ https://issues.apache.org/jira/browse/YARN-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879469#comment-15879469 ] Miklos Szegedi commented on YARN-6218: -- The unit test failure is an unrelated one, YARN-5548. >

[jira] [Updated] (YARN-6218) TestAMRMClient fails with fair scheduler

[ https://issues.apache.org/jira/browse/YARN-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6218: - Attachment: YARN-6218.000.patch Uploading patch. I changed the behavior, so that we test with both

[jira] [Created] (YARN-6218) TestAMRMClient fails with fair scheduler

Miklos Szegedi created YARN-6218: Summary: TestAMRMClient fails with fair scheduler Key: YARN-6218 URL: https://issues.apache.org/jira/browse/YARN-6218 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-6212) NodeManager metrics returning wrong negative values

[ https://issues.apache.org/jira/browse/YARN-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877476#comment-15877476 ] Miklos Szegedi commented on YARN-6212: -- Thank you, [~abkshvn] for reporting this. It may be YARN-3933.

[jira] [Updated] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6171: - Attachment: YARN-6171.004.patch Addressing comments > ConcurrentModificationException in

[jira] [Commented] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868919#comment-15868919 ] Miklos Szegedi commented on YARN-6171: -- Thank you, [~kasha]. Yes, it does. In order to be consistent

[jira] [Updated] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6171: - Attachment: YARN-6171.003.patch Addressing findbugs. > ConcurrentModificationException in

[jira] [Updated] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6171: - Attachment: YARN-6171.002.patch Thank you, [~kasha] for the review. I agree, I fixed these. >

[jira] [Commented] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864725#comment-15864725 ] Miklos Szegedi commented on YARN-6171: -- Notes on tests: TestRMRestart seems to be a flaky test and due

[jira] [Comment Edited] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864294#comment-15864294 ] Miklos Szegedi edited comment on YARN-6171 at 2/13/17 7:46 PM: --- Thank you for

[jira] [Updated] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6171: - Attachment: YARN-6171.001.patch Thank you [~templedf]. I updated the patch. >

[jira] [Updated] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6171: - Attachment: YARN-6171.000.patch > ConcurrentModificationException in

[jira] [Comment Edited] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15861703#comment-15861703 ] Miklos Szegedi edited comment on YARN-6171 at 2/10/17 7:10 PM: --- Based on my

[jira] [Commented] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

[ https://issues.apache.org/jira/browse/YARN-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15861703#comment-15861703 ] Miklos Szegedi commented on YARN-6171: -- Based on my analysis the exception occurs, when containers are

[jira] [Created] (YARN-6171) ConcurrentModificationException in ApplicationMasterService.allocate

Miklos Szegedi created YARN-6171: Summary: ConcurrentModificationException in ApplicationMasterService.allocate Key: YARN-6171 URL: https://issues.apache.org/jira/browse/YARN-6171 Project: Hadoop

[jira] [Commented] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860593#comment-15860593 ] Miklos Szegedi commented on YARN-3933: -- I could not repro the unit test issues above. > Race

[jira] [Commented] (YARN-6169) container-executor message on empty configuration file can be improved

[ https://issues.apache.org/jira/browse/YARN-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860590#comment-15860590 ] Miklos Szegedi commented on YARN-6169: -- It would also be nice to print some additional information in

[jira] [Created] (YARN-6169) container-executor message on empty configuration file can be improved

Miklos Szegedi created YARN-6169: Summary: container-executor message on empty configuration file can be improved Key: YARN-6169 URL: https://issues.apache.org/jira/browse/YARN-6169 Project: Hadoop

[jira] [Commented] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860445#comment-15860445 ] Miklos Szegedi commented on YARN-6144: -- Thank you, [~kasha]. > FairScheduler: preempted resources can

[jira] [Updated] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-3933: - Attachment: YARN-3933.006.patch [~guoshiwei], thank you for looking into this. I ran into the same

[jira] [Comment Edited] (YARN-6158) FairScheduler: app usage can go to negative

[ https://issues.apache.org/jira/browse/YARN-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860301#comment-15860301 ] Miklos Szegedi edited comment on YARN-6158 at 2/9/17 10:18 PM: --- I just

[jira] [Commented] (YARN-6158) FairScheduler: app usage can go to negative

[ https://issues.apache.org/jira/browse/YARN-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860301#comment-15860301 ] Miklos Szegedi commented on YARN-6158: -- I just noticed, think it is the same issue as YARN-3933. This

[jira] [Updated] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6144: - Attachment: YARN-6144.003.patch [~kasha], that is a good point. Updating patch. > FairScheduler:

[jira] [Updated] (YARN-6158) FairScheduler: app usage can go to negative

[ https://issues.apache.org/jira/browse/YARN-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6158: - Attachment: YARN-6158.000.patch Attaching patch. > FairScheduler: app usage can go to negative >

[jira] [Commented] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15858382#comment-15858382 ] Miklos Szegedi commented on YARN-6144: -- I cannot repro

[jira] [Created] (YARN-6158) FairScheduler: app usage can go to negative

Miklos Szegedi created YARN-6158: Summary: FairScheduler: app usage can go to negative Key: YARN-6158 URL: https://issues.apache.org/jira/browse/YARN-6158 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-6135) Node manager REST API documentation is not up to date

[ https://issues.apache.org/jira/browse/YARN-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857148#comment-15857148 ] Miklos Szegedi commented on YARN-6135: -- Thank you for the review and commit [~templedf]! > Node

[jira] [Commented] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856989#comment-15856989 ] Miklos Szegedi commented on YARN-6144: -- Thank you, [~kasha] for the review. I submitted a new patch

[jira] [Updated] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6144: - Attachment: YARN-6144.002.patch > FairScheduler: preempted resources can become negative >

[jira] [Commented] (YARN-6144) FairScheduler: preempted resources can become negative

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854987#comment-15854987 ] Miklos Szegedi commented on YARN-6144: -- About checkstyle: this is a long function that is not a

[jira] [Updated] (YARN-6144) Fair share calculation error

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6144: - Attachment: YARN-6144.001.patch Added some logging. > Fair share calculation error >

[jira] [Commented] (YARN-6144) Fair share calculation error

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852325#comment-15852325 ] Miklos Szegedi commented on YARN-6144: -- [~kasha], could you please take a look? > Fair share

[jira] [Updated] (YARN-6144) Fair share calculation error

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6144: - Attachment: YARN-6144.000.patch Adding a patch to fix this. > Fair share calculation error >

[jira] [Updated] (YARN-6144) Fair share calculation error

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6144: - Attachment: Screen Shot 2017-02-02 at 12.49.14 PM.png The bug can cause unrealistic usage

[jira] [Commented] (YARN-6144) Fair share calculation error

[ https://issues.apache.org/jira/browse/YARN-6144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852174#comment-15852174 ] Miklos Szegedi commented on YARN-6144: -- I think it is related to YARN-4752 > Fair share calculation

[jira] [Created] (YARN-6144) Fair share calculation error

Miklos Szegedi created YARN-6144: Summary: Fair share calculation error Key: YARN-6144 URL: https://issues.apache.org/jira/browse/YARN-6144 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-5665) Documentation does not mention package name requirement for yarn.resourcemanager.scheduler.class

[ https://issues.apache.org/jira/browse/YARN-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15851047#comment-15851047 ] Miklos Szegedi commented on YARN-5665: -- Thank you, [~yufeigu]. I see "Please use a full class patch",

[jira] [Commented] (YARN-4531) org.apache.hadoop.yarn.event.AsyncDispatcher: AsyncDispatcher thread interrupted java.lang.InterruptedException

[ https://issues.apache.org/jira/browse/YARN-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847867#comment-15847867 ] Miklos Szegedi commented on YARN-4531: -- I ran into a similar exception. The impact is that the

[jira] [Commented] (YARN-6056) Yarn NM using LCE shows a failure when trying to delete a non-existing dir

[ https://issues.apache.org/jira/browse/YARN-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836462#comment-15836462 ] Miklos Szegedi commented on YARN-6056: -- Thank you, [~wilfreds]. The patch looks good to me

[jira] [Commented] (YARN-5849) Automatically create YARN control group for pre-mounted cgroups

[ https://issues.apache.org/jira/browse/YARN-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819827#comment-15819827 ] Miklos Szegedi commented on YARN-5849: -- Thank you [~bibinchundatt] for the review and [~templedf] for

[jira] [Assigned] (YARN-3427) Remove deprecated methods from ResourceCalculatorProcessTree

[ https://issues.apache.org/jira/browse/YARN-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi reassigned YARN-3427: Assignee: Miklos Szegedi (was: Karthik Kambatla) > Remove deprecated methods from

[jira] [Updated] (YARN-6077) /bin/bash path is hardcoded in node manager

[ https://issues.apache.org/jira/browse/YARN-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6077: - Description: We need a configuration entry similar to MRJobConfig.MAPRED_ADMIN_USER_SHELL to

[jira] [Commented] (YARN-6077) /bin/bash path is hardcoded in node manager

[ https://issues.apache.org/jira/browse/YARN-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812693#comment-15812693 ] Miklos Szegedi commented on YARN-6077: -- This bug was opened based on the discussion with [~aw] in

[jira] [Commented] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812689#comment-15812689 ] Miklos Szegedi commented on YARN-6060: -- I opened HADOOP-13963 and YARN-6077. Since I am only familiar

[jira] [Created] (YARN-6077) /bin/bash path is hardcoded in node manager

Miklos Szegedi created YARN-6077: Summary: /bin/bash path is hardcoded in node manager Key: YARN-6077 URL: https://issues.apache.org/jira/browse/YARN-6077 Project: Hadoop YARN Issue Type:

[jira] [Resolved] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi resolved YARN-6060. -- Resolution: Won't Fix Assignee: (was: Miklos Szegedi) > Linux container executor fails

[jira] [Commented] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812382#comment-15812382 ] Miklos Szegedi commented on YARN-6060: -- Thank you, [~vvasudev], [~aw] and [~templedf] for the

[jira] [Commented] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15806672#comment-15806672 ] Miklos Szegedi commented on YARN-6060: -- Thank you, [~aw]. Please, remember, I still have the {{#ifdef

[jira] [Commented] (YARN-5936) when cpu strict mode is closed, yarn couldn't assure scheduling fairness between containers

[ https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15806611#comment-15806611 ] Miklos Szegedi commented on YARN-5936: -- In the latest test I used 100 threads per program, I just did

[jira] [Commented] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15806445#comment-15806445 ] Miklos Szegedi commented on YARN-6060: -- Does it help, if we use {{/bin/bash}}? > Linux container

[jira] [Commented] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15806353#comment-15806353 ] Miklos Szegedi commented on YARN-6060: -- Thank you for the comment, [~aw]. As I said, I agree that

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15806273#comment-15806273 ] Miklos Szegedi commented on YARN-5714: -- Thank you for the comment [~templedf]. That option raises the

[jira] [Updated] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6060: - Attachment: YARN-6060.001.patch Attaching a bit bigger patch, if you like this better. It adds the

[jira] [Commented] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15805483#comment-15805483 ] Miklos Szegedi commented on YARN-6060: -- [~aw], I absolutely agree, theoretically Yarn supports native

[jira] [Commented] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802958#comment-15802958 ] Miklos Szegedi commented on YARN-6060: -- test4tests: I checked the patch on a cluster with noexec on

[jira] [Updated] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

[ https://issues.apache.org/jira/browse/YARN-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6060: - Attachment: YARN-6060.000.patch > Linux container executor fails to run container on directories

[jira] [Created] (YARN-6060) Linux container executor fails to run container on directories mounted as noexec

Miklos Szegedi created YARN-6060: Summary: Linux container executor fails to run container on directories mounted as noexec Key: YARN-6060 URL: https://issues.apache.org/jira/browse/YARN-6060

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15796191#comment-15796191 ] Miklos Szegedi commented on YARN-5714: -- The change looks good to me. (non-binding) Thank you,

[jira] [Commented] (YARN-5986) Add support for container specific properties to the ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795882#comment-15795882 ] Miklos Szegedi commented on YARN-5986: -- Thank you, [~vvasudev]! I updated the title. > Add support

[jira] [Updated] (YARN-5986) Add support for container specific properties to the ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5986: - Summary: Add support for container specific properties to the ContainerLaunchContext (was: Adding

[jira] [Commented] (YARN-5987) NM configured command to collect heap dump of preempted container

[ https://issues.apache.org/jira/browse/YARN-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795781#comment-15795781 ] Miklos Szegedi commented on YARN-5987: -- Thank you [~templedf] for the info! YARN-2261 is about adding

[jira] [Commented] (YARN-5936) when cpu strict mode is closed, yarn couldn't assure scheduling fairness between containers

[ https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15762998#comment-15762998 ] Miklos Szegedi commented on YARN-5936: -- Indeed, I see some 6% performance loss in the second case

[jira] [Commented] (YARN-5936) when cpu strict mode is closed, yarn couldn't assure scheduling fairness between containers

[ https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761877#comment-15761877 ] Miklos Szegedi commented on YARN-5936: -- I run 10 of them in parallel. {quote} First，The linux kernel

[jira] [Commented] (YARN-5936) when cpu strict mode is closed, yarn couldn't assure scheduling fairness between containers

[ https://issues.apache.org/jira/browse/YARN-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755361#comment-15755361 ] Miklos Szegedi commented on YARN-5936: -- Thank you, for the reply [~zhengchenyu]! {quote} First，The

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755009#comment-15755009 ] Miklos Szegedi commented on YARN-5714: -- {quote} are you sure about the double % ? i've tested it on

[jira] [Updated] (YARN-5987) NM configured command to collect heap dump of preempted container

[ https://issues.apache.org/jira/browse/YARN-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5987: - Attachment: YARN-5987.001.patch Fixing test issues. > NM configured command to collect heap dump

[jira] [Commented] (YARN-5600) Allow setting yarn.nodemanager.delete.debug-delay-sec on a per-application basis

[ https://issues.apache.org/jira/browse/YARN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15752626#comment-15752626 ] Miklos Szegedi commented on YARN-5600: -- I attached a new patch addressing the comments. > Allow

[jira] [Commented] (YARN-5600) Allow setting yarn.nodemanager.delete.debug-delay-sec on a per-application basis

[ https://issues.apache.org/jira/browse/YARN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15752624#comment-15752624 ] Miklos Szegedi commented on YARN-5600: -- Thank you, [~kasha] for the review! In general about the

[jira] [Updated] (YARN-5600) Allow setting yarn.nodemanager.delete.debug-delay-sec on a per-application basis

[ https://issues.apache.org/jira/browse/YARN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5600: - Attachment: YARN-5600.017.patch > Allow setting yarn.nodemanager.delete.debug-delay-sec on a

[jira] [Updated] (YARN-5600) Allow setting yarn.nodemanager.delete.debug-delay-sec on a per-application basis

[ https://issues.apache.org/jira/browse/YARN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5600: - Attachment: YARN-5600.016.patch Fixing a comment > Allow setting

[jira] [Updated] (YARN-5987) NM configured command to collect heap dump of preempted container

[ https://issues.apache.org/jira/browse/YARN-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5987: - Attachment: YARN-5987.000.patch Since this is a new feature it applies only, if the container is

[jira] [Commented] (YARN-5216) Expose configurable preemption policy for OPPORTUNISTIC containers running on the NM

[ https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746109#comment-15746109 ] Miklos Szegedi commented on YARN-5216: -- [~asuresh], [~hrsharma] Since I was asked, I do not have

[jira] [Commented] (YARN-5714) ContainerExecutor does not order environment map

[ https://issues.apache.org/jira/browse/YARN-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15745900#comment-15745900 ] Miklos Szegedi commented on YARN-5714: -- Thank you, [~rcatherinot] for the reply! 1. {quote} echo %%A%%

[jira] [Updated] (YARN-5849) Automatically create YARN control group for pre-mounted cgroups

[ https://issues.apache.org/jira/browse/YARN-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5849: - Attachment: YARN-5849.008.patch > Automatically create YARN control group for pre-mounted cgroups

[jira] [Commented] (YARN-5849) Automatically create YARN control group for pre-mounted cgroups

[ https://issues.apache.org/jira/browse/YARN-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736662#comment-15736662 ] Miklos Szegedi commented on YARN-5849: -- Thank you, [~bibinchundatt] for the review! I addressed the

[jira] [Commented] (YARN-5986) Adding YARN configuration entries to ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735826#comment-15735826 ] Miklos Szegedi commented on YARN-5986: -- Thank you for the comment [~sjlee0]! No, I am talking only

[jira] [Commented] (YARN-5987) NM configured command to collect heap dump of preempted container

[ https://issues.apache.org/jira/browse/YARN-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734060#comment-15734060 ] Miklos Szegedi commented on YARN-5987: -- The way I would implement this is to let the administrator

[jira] [Updated] (YARN-5987) NM configured command to collect heap dump of preempted container

[ https://issues.apache.org/jira/browse/YARN-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5987: - Summary: NM configured command to collect heap dump of preempted container (was: NM configured

[jira] [Created] (YARN-5987) NM configured command to collect heap dump of preemted container

Miklos Szegedi created YARN-5987: Summary: NM configured command to collect heap dump of preemted container Key: YARN-5987 URL: https://issues.apache.org/jira/browse/YARN-5987 Project: Hadoop YARN

[jira] [Commented] (YARN-5986) Adding YARN configuration entries to ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733685#comment-15733685 ] Miklos Szegedi commented on YARN-5986: -- Please advise, whether this is the right design. > Adding

[jira] [Created] (YARN-5986) Adding YARN configuration entries to ContainerLaunchContext

Miklos Szegedi created YARN-5986: Summary: Adding YARN configuration entries to ContainerLaunchContext Key: YARN-5986 URL: https://issues.apache.org/jira/browse/YARN-5986 Project: Hadoop YARN

[jira] [Commented] (YARN-5600) Add a parameter to ContainerLaunchContext to emulate yarn.nodemanager.delete.debug-delay-sec on a per-application basis

[ https://issues.apache.org/jira/browse/YARN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733405#comment-15733405 ] Miklos Szegedi commented on YARN-5600: -- The unit test issue is YARN-5857

[jira] [Commented] (YARN-5600) Add a parameter to ContainerLaunchContext to emulate yarn.nodemanager.delete.debug-delay-sec on a per-application basis

[ https://issues.apache.org/jira/browse/YARN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732961#comment-15732961 ] Miklos Szegedi commented on YARN-5600: -- The unit test issue is not related to the change. I cannot

[jira] [Updated] (YARN-5600) Add a parameter to ContainerLaunchContext to emulate yarn.nodemanager.delete.debug-delay-sec on a per-application basis

[ https://issues.apache.org/jira/browse/YARN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-5600: - Attachment: YARN-5600.015.patch > Add a parameter to ContainerLaunchContext to emulate >

<    4   5   6   7   8   9   10   11   >