Description
Come on FS. We really don't need to know every time a node with a reservation on it heartbeats.
2014-01-29 03:48:16,043 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler: Trying to fulfill reservation for application appattempt_1390547864213_0347_000001 on node: host: a2330.halxg.cloudera.com:8041 #containers=8 available=<memory:0, vCores:8> used=<memory:8192, vCores:8> 2014-01-29 03:48:16,043 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AppSchedulable: Making reservation: node=a2330.halxg.cloudera.com app_id=application_1390547864213_0347 2014-01-29 03:48:16,043 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt: Application application_1390547864213_0347 reserved container container_1390547864213_0347_01_000003 on node host: a2330.halxg.cloudera.com:8041 #containers=8 available=<memory:0, vCores:8> used=<memory:8192, vCores:8>, currently has 6 at priority 0; currentReservation 6144 2014-01-29 03:48:16,044 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode: Updated reserved container container_1390547864213_0347_01_000003 on node host: a2330.halxg.cloudera.com:8041 #containers=8 available=<memory:0, vCores:8> used=<memory:8192, vCores:8> for application org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerApp@1cb01d20