[jira] [Commented] (YARN-983) ApplicationReport can return tokens only when users asks for it explicitly
[ https://issues.apache.org/jira/browse/YARN-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721828#comment-13721828 ] Alejandro Abdelnur commented on YARN-983: - Wouldn't the same apply for the client token? > ApplicationReport can return tokens only when users asks for it explicitly > -- > > Key: YARN-983 > URL: https://issues.apache.org/jira/browse/YARN-983 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vinod Kumar Vavilapalli > > There is no need for ApplicationReport to always fetch client and AMtoRM > Tokens (in case of UnmanagedAMs) everytime ApplicationReport is requested. We > can send it only when users explicitly asks for it via a new field in > GetApplicationReportRequest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk
[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721762#comment-13721762 ] Alejandro Abdelnur commented on YARN-960: - Thanks [~vinodkv], this problem seems to be gone, but now there is another one, opened MAPREDUCE-5426 for it. > TestMRCredentials and TestBinaryTokenFile are failing on trunk > --- > > Key: YARN-960 > URL: https://issues.apache.org/jira/browse/YARN-960 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 2.1.0-beta >Reporter: Alejandro Abdelnur >Assignee: Daryn Sharp >Priority: Blocker > Fix For: 2.1.0-beta > > Attachments: YARN-960.patch > > > Not sure, but this may be a fallout from YARN-701 and/or related to YARN-945. > Making it a blocker until full impact of the issue is scoped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-983) ApplicationReport can return tokens only when users asks for it explicitly
[ https://issues.apache.org/jira/browse/YARN-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721757#comment-13721757 ] Vinod Kumar Vavilapalli commented on YARN-983: -- There is ClientToken too like I mentioned in the description. > ApplicationReport can return tokens only when users asks for it explicitly > -- > > Key: YARN-983 > URL: https://issues.apache.org/jira/browse/YARN-983 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vinod Kumar Vavilapalli > > There is no need for ApplicationReport to always fetch client and AMtoRM > Tokens (in case of UnmanagedAMs) everytime ApplicationReport is requested. We > can send it only when users explicitly asks for it via a new field in > GetApplicationReportRequest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-983) ApplicationReport can return tokens only when users asks for it explicitly
[ https://issues.apache.org/jira/browse/YARN-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721755#comment-13721755 ] Alejandro Abdelnur commented on YARN-983: - Do we need an additional request field to indicate we want it? The current logic already: * returns the AMMR token only for unmanaged AMs * the AMRM token only when in ACCEPTED state Typically you 'monitor' the state of your launch AM until gets to ACCEPTED they you proceed to register, thus effectively the AMRM token will be returned only once. Plus, unmanaged AMs need the AMRM token, so asking them to say they want it seems a bit redundant. > ApplicationReport can return tokens only when users asks for it explicitly > -- > > Key: YARN-983 > URL: https://issues.apache.org/jira/browse/YARN-983 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Vinod Kumar Vavilapalli > > There is no need for ApplicationReport to always fetch client and AMtoRM > Tokens (in case of UnmanagedAMs) everytime ApplicationReport is requested. We > can send it only when users explicitly asks for it via a new field in > GetApplicationReportRequest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (YARN-983) ApplicationReport can return tokens only when users asks for it explicitly
Vinod Kumar Vavilapalli created YARN-983: Summary: ApplicationReport can return tokens only when users asks for it explicitly Key: YARN-983 URL: https://issues.apache.org/jira/browse/YARN-983 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli There is no need for ApplicationReport to always fetch client and AMtoRM Tokens (in case of UnmanagedAMs) everytime ApplicationReport is requested. We can send it only when users explicitly asks for it via a new field in GetApplicationReportRequest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701
[ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur resolved YARN-937. - Resolution: Fixed Hadoop Flags: Reviewed Committed to trunk, branch-2 and branch-2.1. Also, created YARN-982 to add method to get address from client proxy instead re-reading config. > Fix unmanaged AM in non-secure/secure setup post YARN-701 > - > > Key: YARN-937 > URL: https://issues.apache.org/jira/browse/YARN-937 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 2.1.0-beta >Reporter: Arun C Murthy >Assignee: Alejandro Abdelnur >Priority: Blocker > Fix For: 2.1.0-beta > > Attachments: YARN-937.patch, YARN-937.patch, YARN-937.patch, > YARN-937.patch, YARN-937.patch, YARN-937.patch > > > Fix unmanaged AM in non-secure/secure setup post YARN-701 since app-tokens > will be used in both scenarios. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (YARN-982) Add method in client to provide address of service(s) in use
Alejandro Abdelnur created YARN-982:
---
Summary: Add method in client to provide address of service(s) in
use
Key: YARN-982
URL: https://issues.apache.org/jira/browse/YARN-982
Project: Hadoop YARN
Issue Type: Improvement
Components: client
Affects Versions: 2.1.0-beta
Reporter: Alejandro Abdelnur
As discussed in YARN-937, there should be a way from getting from the
{{ClientRMProxy}} {{ApplicationClientProtocol}} the addresses of the RM in use
instead rereading them from configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk
[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721713#comment-13721713 ] Vinod Kumar Vavilapalli commented on YARN-960: -- Checking this in. [~tucu00], please see [my comment|https://issues.apache.org/jira/browse/YARN-960?focusedCommentId=13721064&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13721064] and feel free to reopen it if things don't work for you yet. > TestMRCredentials and TestBinaryTokenFile are failing on trunk > --- > > Key: YARN-960 > URL: https://issues.apache.org/jira/browse/YARN-960 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 2.1.0-beta >Reporter: Alejandro Abdelnur >Assignee: Daryn Sharp >Priority: Blocker > Fix For: 2.1.0-beta > > Attachments: YARN-960.patch > > > Not sure, but this may be a fallout from YARN-701 and/or related to YARN-945. > Making it a blocker until full impact of the issue is scoped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (YARN-84) Use Builder to get RPC server in YARN
[ https://issues.apache.org/jira/browse/YARN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-84: Fix Version/s: (was: 3.0.0) 2.1.0-beta > Use Builder to get RPC server in YARN > - > > Key: YARN-84 > URL: https://issues.apache.org/jira/browse/YARN-84 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Brandon Li >Assignee: Brandon Li >Priority: Minor > Fix For: 2.1.0-beta > > Attachments: MAPREDUCE-4628.patch, YARN-84-branch2.patch > > > In HADOOP-8736, a Builder is introduced to replace all the getServer() > variants. This JIRA is the change in YARN. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
