[YARN-5297] Avoid printing a stack trace when recovering an app after the RM restarts

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-alpha1
• Hadoop Flags: Reviewed
• Assignee: Junping Du
• Reporter: Siddharth Seth
• Created: 27/Jun/16 17:36
• Updated: 25/Oct/19 20:27
• Resolved: 08/Jul/16 20:09

Description

The exception trace is unnecessary, and can cause confusion.

2016-06-16 22:02:54,262 INFO  ipc.Server (Server.java:logException(2401)) - IPC Server handler 0 on 8030, call org.apache.hadoop.yarn.api.ApplicationMasterProtocolPB.allocate from 172.22.79.149:42698 Call#2241 Retry#0
org.apache.hadoop.yarn.exceptions.ApplicationMasterNotRegisteredException: AM is not registered for known application attempt: appattempt_1466112179488_0001_000001 or RM had restarted after AM registered . AM should re-register.
  at org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService.allocate(ApplicationMasterService.java:454)
  at org.apache.hadoop.yarn.api.impl.pb.service.ApplicationMasterProtocolPBServiceImpl.allocate(ApplicationMasterProtocolPBServiceImpl.java:60)
  at org.apache.hadoop.yarn.proto.ApplicationMasterProtocol$ApplicationMasterProtocolService$2.callBlockingMethod(ApplicationMasterProtocol.java:99)
  at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
  at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
  at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2313)
  at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2309)
  at java.security.AccessController.doPrivileged(Native Method)
  at javax.security.auth.Subject.doAs(Subject.java:422)
  at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724)
  at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2307)

cc djp