Hi Jeff, To get the AMRMToken, you can use YarnClient#getAMRMToken. For unmanaged application, you can have look at UnmanagedAMLauncher, you didn't check it before. It may simplify your problem
- Zhijie On Tue, Feb 25, 2014 at 9:38 PM, Jeff Zhang <[email protected]> wrote: > Hi all, > > I build an ummanaged application and submit it to yarn ( hadoop 2.2). But > encounter the following exception: > > Caused by: > org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): > SIMPLE authentication is not enabled. Available:[TOKEN] > > at org.apache.hadoop.ipc.Client.call(Client.java:1347) > > at org.apache.hadoop.ipc.Client.call(Client.java:1300) > > at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke( > ProtobufRpcEngine.java:206) > > at $Proxy9.registerApplicationMaster(Unknown Source) > > at > org.apache.hadoop.yarn.api.impl.pb.client.ApplicationMasterProtocolPBClientImpl.registerApplicationMaster( > ApplicationMasterProtocolPBClientImpl.java:106) > I find there's one jira ticket very similar to this issue, but looks like > it has been resolved in 2.2 > https://issues.apache.org/jira/browse/YARN-945 > > > I find that ResourceTrackerService will use simple authentication but > ApplicationMasterService will use token. The reason I think is at the > following code snippet in ApplicationMasterSerivce ( line 127 ) > serverConf.set( > > CommonConfigurationKeysPublic.HADOOP_SECURITY_AUTHENTICATION, > > SaslRpcServer.AuthMethod.TOKEN.toString()); > > > I'm not sure why here use the token, could any help explain that and guide > me how to resolve my issue? Thanks > > > Jeff Zhang > > > > -- Zhijie Shen Hortonworks Inc. http://hortonworks.com/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
