[jira] [Updated] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-661: --- Attachment: YARN-661-20130711.1.patch NM fails to cleanup local directories for users

[jira] [Commented] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

[ https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706197#comment-13706197 ] Omkar Vinit Joshi commented on YARN-744: [~bikassaha] sounds reasonable ..will take

[jira] [Commented] (YARN-897) CapacityScheduler wrongly sorted queues

[ https://issues.apache.org/jira/browse/YARN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706284#comment-13706284 ] Omkar Vinit Joshi commented on YARN-897: [~dedcode] Thanks for posting the patch...

[jira] [Created] (YARN-916) JobContext cache files api are broken

Omkar Vinit Joshi created YARN-916: -- Summary: JobContext cache files api are broken Key: YARN-916 URL: https://issues.apache.org/jira/browse/YARN-916 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-897) CapacityScheduler wrongly sorted queues

[ https://issues.apache.org/jira/browse/YARN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706488#comment-13706488 ] Omkar Vinit Joshi commented on YARN-897: [~dedcode] please do keep older patches...

[jira] [Updated] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

[ https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-744: --- Attachment: YARN-744-20130711.1.patch Race condition in ApplicationMasterService.allocate

[jira] [Commented] (YARN-592) Container logs lost for the application when NM gets restarted

[ https://issues.apache.org/jira/browse/YARN-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706495#comment-13706495 ] Omkar Vinit Joshi commented on YARN-592: Just to be sure I might be wrong I am

[jira] [Resolved] (YARN-541) getAllocatedContainers() is not returning all the allocated containers

[ https://issues.apache.org/jira/browse/YARN-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-541. Resolution: Invalid getAllocatedContainers() is not returning all the allocated

[jira] [Commented] (YARN-541) getAllocatedContainers() is not returning all the allocated containers

[ https://issues.apache.org/jira/browse/YARN-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706506#comment-13706506 ] Omkar Vinit Joshi commented on YARN-541: I am closing this as invalid... please

[jira] [Commented] (YARN-701) ApplicationTokens should be used irrespective of kerberos

[ https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706561#comment-13706561 ] Omkar Vinit Joshi commented on YARN-701: I have checked the patch some comments *

[jira] [Updated] (YARN-701) ApplicationTokens should be used irrespective of kerberos

[ https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-701: --- Attachment: yarn-ojoshi-resourcemanager-HW10351.local.log ApplicationTokens should be

[jira] [Assigned] (YARN-541) getAllocatedContainers() is not returning all the allocated containers

[ https://issues.apache.org/jira/browse/YARN-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-541: -- Assignee: Omkar Vinit Joshi getAllocatedContainers() is not returning all the

[jira] [Assigned] (YARN-523) Container localization failures aren't reported from NM to RM

[ https://issues.apache.org/jira/browse/YARN-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-523: -- Assignee: Jian He (was: Omkar Vinit Joshi) Container localization failures aren't

[jira] [Assigned] (YARN-389) Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity

[ https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-389: -- Assignee: Omkar Vinit Joshi (was: Zhijie Shen) Infinitely assigning containers

[jira] [Commented] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13705393#comment-13705393 ] Omkar Vinit Joshi commented on YARN-661: Thanks [~zjshen] .. uploading updated

[jira] [Updated] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-661: --- Attachment: YARN-661-20130710.1.patch NM fails to cleanup local directories for users

[jira] [Commented] (YARN-299) Node Manager throws org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: RESOURCE_FAILED at DONE

[ https://issues.apache.org/jira/browse/YARN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703639#comment-13703639 ] Omkar Vinit Joshi commented on YARN-299: as a good practice it is good to grab lock

[jira] [Commented] (YARN-299) Node Manager throws org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: RESOURCE_FAILED at DONE

[ https://issues.apache.org/jira/browse/YARN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703820#comment-13703820 ] Omkar Vinit Joshi commented on YARN-299: my bad... missed it...canceling the patch..

[jira] [Assigned] (YARN-203) Fixup ResourceLocalizationService

[ https://issues.apache.org/jira/browse/YARN-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-203: -- Assignee: Omkar Vinit Joshi Fixup ResourceLocalizationService

[jira] [Assigned] (YARN-241) Node Manager fails to launch containers after NM restart in secure mode

[ https://issues.apache.org/jira/browse/YARN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-241: -- Assignee: Omkar Vinit Joshi (was: Devaraj K) Node Manager fails to launch

[jira] [Commented] (YARN-241) Node Manager fails to launch containers after NM restart in secure mode

[ https://issues.apache.org/jira/browse/YARN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703961#comment-13703961 ] Omkar Vinit Joshi commented on YARN-241: [~devaraj.k] taking over... any idea how to

[jira] [Resolved] (YARN-190) Issues when running distributedShell example in hadoop-2.0.1-alpha cluster

[ https://issues.apache.org/jira/browse/YARN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-190. Resolution: Cannot Reproduce Issues when running distributedShell example in

[jira] [Commented] (YARN-190) Issues when running distributedShell example in hadoop-2.0.1-alpha cluster

[ https://issues.apache.org/jira/browse/YARN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13704036#comment-13704036 ] Omkar Vinit Joshi commented on YARN-190: [~xiajunluan] there were major changes in

[jira] [Assigned] (YARN-194) Log handling in case of NM restart.

[ https://issues.apache.org/jira/browse/YARN-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-194: -- Assignee: Omkar Vinit Joshi Log handling in case of NM restart.

[jira] [Commented] (YARN-194) Log handling in case of NM restart.

[ https://issues.apache.org/jira/browse/YARN-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13704053#comment-13704053 ] Omkar Vinit Joshi commented on YARN-194: we may or may not want to delete the logs

[jira] [Commented] (YARN-182) Unnecessary Container killed by the ApplicationMaster message for successful containers

[ https://issues.apache.org/jira/browse/YARN-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13704056#comment-13704056 ] Omkar Vinit Joshi commented on YARN-182: Closing this as duplicate as YARN-903 shows

[jira] [Assigned] (YARN-182) Unnecessary Container killed by the ApplicationMaster message for successful containers

[ https://issues.apache.org/jira/browse/YARN-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-182: -- Assignee: Omkar Vinit Joshi Unnecessary Container killed by the ApplicationMaster

[jira] [Resolved] (YARN-182) Unnecessary Container killed by the ApplicationMaster message for successful containers

[ https://issues.apache.org/jira/browse/YARN-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-182. Resolution: Duplicate Unnecessary Container killed by the ApplicationMaster message for

[jira] [Commented] (YARN-903) DistributedShell throwing Errors in logs after successfull completion

[ https://issues.apache.org/jira/browse/YARN-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13704069#comment-13704069 ] Omkar Vinit Joshi commented on YARN-903: yes looks like the exception is

[jira] [Assigned] (YARN-455) NM warns about stopping an unknown container under normal circumstances

[ https://issues.apache.org/jira/browse/YARN-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-455: -- Assignee: Omkar Vinit Joshi NM warns about stopping an unknown container under

[jira] [Commented] (YARN-241) Node Manager fails to launch containers after NM restart in secure mode

[ https://issues.apache.org/jira/browse/YARN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13704088#comment-13704088 ] Omkar Vinit Joshi commented on YARN-241: [~devaraj.k] closing it as not

[jira] [Resolved] (YARN-241) Node Manager fails to launch containers after NM restart in secure mode

[ https://issues.apache.org/jira/browse/YARN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-241. Resolution: Cannot Reproduce Recent changes have changed the behavior and is no longer

[jira] [Commented] (YARN-685) Capacity Scheduler is not distributing the reducers tasks across the cluster

[ https://issues.apache.org/jira/browse/YARN-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13704102#comment-13704102 ] Omkar Vinit Joshi commented on YARN-685: I would like to take this up...is there

[jira] [Commented] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702158#comment-13702158 ] Omkar Vinit Joshi commented on YARN-644: [~josephkniest] in these scenarios we

[jira] [Commented] (YARN-245) Node Manager gives InvalidStateTransitonException for FINISH_APPLICATION at FINISHED

[ https://issues.apache.org/jira/browse/YARN-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702308#comment-13702308 ] Omkar Vinit Joshi commented on YARN-245: I think this will not fix the root cause.

[jira] [Commented] (YARN-299) Node Manager throws org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: RESOURCE_FAILED at DONE

[ https://issues.apache.org/jira/browse/YARN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702456#comment-13702456 ] Omkar Vinit Joshi commented on YARN-299: I guess the patch looks good overall ..

[jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702532#comment-13702532 ] Omkar Vinit Joshi commented on YARN-814: * Instead of putting string messages of

[jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702646#comment-13702646 ] Omkar Vinit Joshi commented on YARN-814: * yeah... what I am saying is user can

[jira] [Updated] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-661: --- Attachment: YARN-661-20130708.patch NM fails to cleanup local directories for users

[jira] [Commented] (YARN-592) Container logs lost for the application when NM gets restarted

[ https://issues.apache.org/jira/browse/YARN-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702823#comment-13702823 ] Omkar Vinit Joshi commented on YARN-592: I just looked at your patch I need more

[jira] [Updated] (YARN-903) DistributedShell throwing Errors in logs after successfull completion

[ https://issues.apache.org/jira/browse/YARN-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-903: --- Assignee: Omkar Vinit Joshi DistributedShell throwing Errors in logs after successfull

[jira] [Commented] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13698518#comment-13698518 ] Omkar Vinit Joshi commented on YARN-661: * First part..very much straight forward..

[jira] [Updated] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-661: --- Attachment: YARN-661-20130701.patch NM fails to cleanup local directories for users

[jira] [Updated] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-864: --- Assignee: Jian He YARN NM leaking containers with CGroups

[jira] [Commented] (YARN-712) RMDelegationTokenSecretManager shouldn't start in non-secure mode

[ https://issues.apache.org/jira/browse/YARN-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13697069#comment-13697069 ] Omkar Vinit Joshi commented on YARN-712: can we enable it irrespective of security?

[jira] [Assigned] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-661: -- Assignee: Omkar Vinit Joshi NM fails to cleanup local directories for users

[jira] [Commented] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13697277#comment-13697277 ] Omkar Vinit Joshi commented on YARN-661: taking this over... Just reproduced this

[jira] [Commented] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13697320#comment-13697320 ] Omkar Vinit Joshi commented on YARN-661: I guess we need 2 features in deletion

[jira] [Updated] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

[ https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-744: --- Summary: Race condition in ApplicationMasterService.allocate .. It might process same allocate

[jira] [Commented] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

[ https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13695706#comment-13695706 ] Omkar Vinit Joshi commented on YARN-744: The problem here is that we retrieve the

[jira] [Updated] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

[ https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-744: --- Attachment: YARN-744.patch Race condition in ApplicationMasterService.allocate .. It

[jira] [Resolved] (YARN-718) Remove RemoteUGI.getRemoteUser check from startContainer in ContainerManagerImpl as this is no longer required

[ https://issues.apache.org/jira/browse/YARN-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-718. Resolution: Invalid YARN-613 fixes this.. getUser is required and containerId is replaced by

[jira] [Commented] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13695883#comment-13695883 ] Omkar Vinit Joshi commented on YARN-62: --- fixing test issues... AM

[jira] [Updated] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-62: -- Attachment: YARN-62-20130628.patch AM should not be able to abuse container tokens for

[jira] [Updated] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-62: -- Attachment: (was: YARN-62-20130628.patch) AM should not be able to abuse container

[jira] [Updated] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-62: -- Attachment: YARN-62-20130628.patch AM should not be able to abuse container tokens for

[jira] [Updated] (YARN-701) ApplicationTokens should be used irrespective of kerberos

[ https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-701: --- Priority: Major (was: Blocker) ApplicationTokens should be used irrespective of kerberos

[jira] [Commented] (YARN-701) ApplicationTokens should be used irrespective of kerberos

[ https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693696#comment-13693696 ] Omkar Vinit Joshi commented on YARN-701: changing it back to major from blocker as

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693593#comment-13693593 ] Omkar Vinit Joshi commented on YARN-873: I think the client should get an error code

[jira] [Commented] (YARN-554) YARN with security enabled read local block failed

[ https://issues.apache.org/jira/browse/YARN-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693594#comment-13693594 ] Omkar Vinit Joshi commented on YARN-554: is this valid on trunk?

[jira] [Updated] (YARN-882) Specify per user quota for private/application cache and user log files

[ https://issues.apache.org/jira/browse/YARN-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-882: --- Description: At present there is no limit on the number of files / size of the files

[jira] [Created] (YARN-882) Specify per user quota for private/application cache and user log files

Omkar Vinit Joshi created YARN-882: -- Summary: Specify per user quota for private/application cache and user log files Key: YARN-882 URL: https://issues.apache.org/jira/browse/YARN-882 Project:

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692525#comment-13692525 ] Omkar Vinit Joshi commented on YARN-884: Probably these two are unrelated. First if

[jira] [Commented] (YARN-874) Tracking YARN/MR test failures after HADOOP-9421 and YARN-827

[ https://issues.apache.org/jira/browse/YARN-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692664#comment-13692664 ] Omkar Vinit Joshi commented on YARN-874: tested YARN-872-2...on local cluster...

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692668#comment-13692668 ] Omkar Vinit Joshi commented on YARN-884: [~kkambatl] makes sense...

[jira] [Resolved] (YARN-870) Node manager is no longer required to store ContainerToken as it is required only during startContainer call.

[ https://issues.apache.org/jira/browse/YARN-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-870. Resolution: Duplicate Fixing this will also fix YARN-62. attaching patch there as it is

[jira] [Commented] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690805#comment-13690805 ] Omkar Vinit Joshi commented on YARN-62: --- Right now on NM we start container only when

[jira] [Commented] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690799#comment-13690799 ] Omkar Vinit Joshi commented on YARN-62: --- Fixing this as a part of YARN-870. attaching

[jira] [Assigned] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-62: - Assignee: Omkar Vinit Joshi (was: Vinod Kumar Vavilapalli) AM should not be able to

[jira] [Updated] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-62: -- Attachment: YARN-62-20130621.patch AM should not be able to abuse container tokens for

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690935#comment-13690935 ] Omkar Vinit Joshi commented on YARN-864: Also it would be very useful if you can

[jira] [Updated] (YARN-62) AM should not be able to abuse container tokens for repetitive container launches

[ https://issues.apache.org/jira/browse/YARN-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-62: -- Attachment: YARN-62-20130621.1.patch AM should not be able to abuse container tokens for

[jira] [Updated] (YARN-701) ApplicationTokens should be used irrespective of kerberos

[ https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-701: --- Priority: Blocker (was: Major) ApplicationTokens should be used irrespective of kerberos

[jira] [Updated] (YARN-701) ApplicationTokens should be used irrespective of kerberos

[ https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-701: --- Affects Version/s: 2.1.0-beta ApplicationTokens should be used irrespective of kerberos

[jira] [Commented] (YARN-862) ResourceManager and NodeManager versions should match on node registration or error out

[ https://issues.apache.org/jira/browse/YARN-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689496#comment-13689496 ] Omkar Vinit Joshi commented on YARN-862: Won't this become a problem in case we are

[jira] [Updated] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130619.patch Share NMTokens using NMTokenCache (api-based) instead

[jira] [Updated] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130620.patch Share NMTokens using NMTokenCache (api-based) instead

[jira] [Updated] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: (was: YARN-851-20130620.patch) Share NMTokens using NMTokenCache

[jira] [Commented] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689792#comment-13689792 ] Omkar Vinit Joshi commented on YARN-851: fixing vinod's comments. marking class and

[jira] [Updated] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130620.1.patch Share NMTokens using NMTokenCache (api-based)

[jira] [Updated] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130620.2.patch Share NMTokens using NMTokenCache (api-based)

[jira] [Commented] (YARN-738) TestClientRMTokens is failing irregularly while running all yarn tests

[ https://issues.apache.org/jira/browse/YARN-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689884#comment-13689884 ] Omkar Vinit Joshi commented on YARN-738: looks like it is fixed for now.. please

[jira] [Resolved] (YARN-738) TestClientRMTokens is failing irregularly while running all yarn tests

[ https://issues.apache.org/jira/browse/YARN-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-738. Resolution: Invalid Assignee: Omkar Vinit Joshi TestClientRMTokens is failing

[jira] [Assigned] (YARN-35) Move to per-node RM-NM secrets

[ https://issues.apache.org/jira/browse/YARN-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-35: - Assignee: Omkar Vinit Joshi Move to per-node RM-NM secrets

[jira] [Created] (YARN-870) Node manager is no longer required to store ContainerToken as it is required only during startContainer call.

Omkar Vinit Joshi created YARN-870: -- Summary: Node manager is no longer required to store ContainerToken as it is required only during startContainer call. Key: YARN-870 URL:

[jira] [Updated] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-854: --- Attachment: YARN-854.20130619.patch App submission fails on secure deploy

[jira] [Commented] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688588#comment-13688588 ] Omkar Vinit Joshi commented on YARN-854: Fixing one more thing.. making sure

[jira] [Updated] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-854: --- Attachment: YARN-854.20130619.1.patch App submission fails on secure deploy

[jira] [Updated] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-854: --- Attachment: YARN-854.20130619.2.patch App submission fails on secure deploy

[jira] [Updated] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130619.patch Share NMTokens using NMTokenCache (api-based) instead

[jira] [Commented] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688812#comment-13688812 ] Omkar Vinit Joshi commented on YARN-851: Fixed above comments. removed

[jira] [Updated] (YARN-694) Start using NMTokens to authenticate all communication with NM

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.patch Start using NMTokens to authenticate all

[jira] [Updated] (YARN-694) Start using NMTokens to authenticate all communication with NM

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.1.patch Start using NMTokens to authenticate all

[jira] [Updated] (YARN-694) Start using NMTokens to authenticate all communication with NM

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Attachment: (was: YARN-694-20130618.patch) Start using NMTokens to authenticate all

[jira] [Updated] (YARN-694) Start using NMTokens to authenticate all communication with NM

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.2.patch Start using NMTokens to authenticate all

[jira] [Updated] (YARN-694) Start using NMTokens to authenticate all communication with NM

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.3.patch Start using NMTokens to authenticate all

[jira] [Updated] (YARN-694) Start using NMTokens to authenticate all communication with NM

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.4.patch Start using NMTokens to authenticate all

[jira] [Updated] (YARN-694) Start using NMTokens to authenticate all communication with NM

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.5.patch Start using NMTokens to authenticate all

[jira] [Resolved] (YARN-739) NM startContainer should validate the NodeId

[ https://issues.apache.org/jira/browse/YARN-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-739. Resolution: Fixed Fix Version/s: 2.1.0-beta NM startContainer should validate

[jira] [Commented] (YARN-739) NM startContainer should validate the NodeId

[ https://issues.apache.org/jira/browse/YARN-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687272#comment-13687272 ] Omkar Vinit Joshi commented on YARN-739: YARN-694 fixes this. closing this

<    1   2   3   4   5   6   7   8   >