[YARN-142] [Umbrella] Cleanup YARN APIs w.r.t exceptions

• Type: Task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.23.3, 2.0.0-alpha
• Fix Version/s: 2.1.0-beta
• Target Version/s: 2.1.0-beta
• Assignee: Unassigned
• Reporter: Siddharth Seth
• Created: 03/Oct/12 20:33
• Updated: 27/Aug/13 22:15
• Resolved: 11/Jun/13 22:37

Description

Ref: MAPREDUCE-4067

All YARN APIs currently throw YarnRemoteException.
1) This cannot be extended in it's current form.
2) The RPC layer can throw IOExceptions. These end up showing up as UndeclaredThrowableExceptions.

Issue Links

• blocks: MAPREDUCE-4067 Replace YarnRemoteException with IOException in MRv2 APIs
• is related to: YARN-386 [Umbrella] YARN API Changes
• is related to: YARN-627 Simplify YarnRemoteException to not be backed by PB
• relates to: HADOOP-9343 Allow additional exceptions through the RPC layer

Sub-Tasks

• Change ContainerManagerPBClientImpl and RMAdminProtocolPBClientImpl to throw IOException and YarnRemoteException: Closed
• Fix YarnException unwrapping: Closed
• Change ClientRMProtocol api to throw IOException and YarnRemoteException: Closed
• Make YarnRemoteException not backed by PB and introduce a SerializedException: Closed
• Change AMRMProtocol api to throw IOException and YarnRemoteException: Closed
• Make YarnRemoteException not be rooted at IOException: Closed
• Change ContainerManager api to throw IOException and YarnRemoteException: Closed
• Change RMAdminProtocol api to throw IOException and YarnRemoteException: Closed
• Move unwrapAndThrowException from YarnRemoteExceptionPBImpl to RPCUtil: Closed
• Rename YarnRemoteException to YarnException: Closed
• Change ResourceTracker API and LocalizationProtocol API to throw YarnRemoteException and IOException: Closed
• RPCUtil.unwrapAndThrowException should unwrap remote RuntimeExceptions: Closed