[MAPREDUCE-6761] Regression when handling providers - invalid configuration ServiceConfiguration causes Cluster initialization failure

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha2
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: mrv2
• Labels: supportability
• Hadoop Flags: Reviewed
• Assignee: Peter Vary
• Reporter: Peter Vary
• Created: 19/Aug/16 01:03
• Updated: 30/Aug/16 01:13
• Resolved: 24/Aug/16 14:44

Description

When a rogue org.apache.hadoop.mapreduce.protocol.ClientProtocolProvider defines a provider that is not on classpath, then the initialization is failed with the following exception:

java.util.ServiceConfigurationError: org.apache.hadoop.mapreduce.protocol.ClientProtocolProvider: Provider org.apache.hadoop.mapred.YarnClientProtocolProvider not found
at java.util.ServiceLoader.fail(ServiceLoader.java:239)
at java.util.ServiceLoader.access$300(ServiceLoader.java:185)
at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:372)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
at org.apache.hadoop.mapreduce.Cluster.initProviderList(Cluster.java:84)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:114)
at org.apache.hadoop.mapreduce.Cluster.<init>(Cluster.java:108)
at org.apache.hadoop.mapreduce.Cluster.<init>(Cluster.java:101)
at org.apache.hadoop.mapred.JobClient.init(JobClient.java:477)
at org.apache.hadoop.mapred.JobClient.<init>(JobClient.java:455)

This regression is caused by MAPREDUCE-6473

Issue Links

• is related to: MAPREDUCE-6473 Job submission can take a long time during Cluster initialization