YARN-8369. Javadoc build failed due to 'bad use of >'. (Takanobu Asanuma via wangda)

Change-Id: I79a42154e8f86ab1c3cc939b3745024b8eebe5f4
(cherry picked from commit 17aa40f669)
This commit is contained in:
Wangda Tan 2018-05-29 09:27:36 -07:00
parent b262ea1381
commit 3eb1cb18c7
2 changed files with 6 additions and 6 deletions

View File

@ -260,10 +260,10 @@ public abstract class ResourceCalculator {
/** /**
* Check if resource has any major resource types (which are all NodeManagers * Check if resource has any major resource types (which are all NodeManagers
* included) has a >0 value. * included) has a {@literal >} 0 value.
* *
* @param resource resource * @param resource resource
* @return returns true if any resource is >0 * @return returns true if any resource is {@literal >} 0
*/ */
public abstract boolean isAnyMajorResourceAboveZero(Resource resource); public abstract boolean isAnyMajorResourceAboveZero(Resource resource);
} }

View File

@ -136,12 +136,12 @@ public class CapacitySchedulerPreemptionUtils {
* @param conservativeDRF * @param conservativeDRF
* should we do conservativeDRF preemption or not. * should we do conservativeDRF preemption or not.
* When true: * When true:
* stop preempt container when any major resource type <= 0 for to- * stop preempt container when any major resource type
* preempt. * {@literal <=} 0 for to-preempt.
* This is default preemption behavior of intra-queue preemption * This is default preemption behavior of intra-queue preemption
* When false: * When false:
* stop preempt container when: all major resource type <= 0 for * stop preempt container when: all major resource type
* to-preempt. * {@literal <=} 0 for to-preempt.
* This is default preemption behavior of inter-queue preemption * This is default preemption behavior of inter-queue preemption
* @return should we preempt rmContainer. If we should, deduct from * @return should we preempt rmContainer. If we should, deduct from
* <code>resourceToObtainByPartition</code> * <code>resourceToObtainByPartition</code>