YARN-2243. Order of arguments for Preconditions.checkNotNull() is wrong in
SchedulerApplicationAttempt ctor. Contributed by Devaraj K.
(cherry picked from commit bda748ac3a
)
This commit is contained in:
parent
25f4a0193b
commit
10ff600b35
|
@ -185,6 +185,9 @@ Release 2.7.0 - UNRELEASED
|
|||
YARN-2917. Fixed potential deadlock when system.exit is called in AsyncDispatcher
|
||||
(Rohith Sharmaks via jianhe)
|
||||
|
||||
YARN-2243. Order of arguments for Preconditions.checkNotNull() is wrong in
|
||||
SchedulerApplicationAttempt ctor. (devaraj)
|
||||
|
||||
Release 2.6.0 - 2014-11-18
|
||||
|
||||
INCOMPATIBLE CHANGES
|
||||
|
|
|
@ -125,7 +125,7 @@ public class SchedulerApplicationAttempt {
|
|||
public SchedulerApplicationAttempt(ApplicationAttemptId applicationAttemptId,
|
||||
String user, Queue queue, ActiveUsersManager activeUsersManager,
|
||||
RMContext rmContext) {
|
||||
Preconditions.checkNotNull("RMContext should not be null", rmContext);
|
||||
Preconditions.checkNotNull(rmContext, "RMContext should not be null");
|
||||
this.rmContext = rmContext;
|
||||
this.appSchedulingInfo =
|
||||
new AppSchedulingInfo(applicationAttemptId, user, queue,
|
||||
|
|
Loading…
Reference in New Issue