You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Karam Singh (JIRA)" <ji...@apache.org> on 2008/10/21 16:19:46 UTC
[jira] Issue Comment Edited: (HADOOP-4444) Scheduling Information
for queues shows one map/reduce task less then actual running map/reduce
tasks.
[ https://issues.apache.org/jira/browse/HADOOP-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640514#action_12640514 ]
karams edited comment on HADOOP-4444 at 10/21/08 7:18 AM:
---------------------------------------------------------------
Submitted a job with map and reduce tasks = 212.
When all maps and reduces tasks of job starts running, JobTracker UI displayed following information about "Cluster Summary" and "Scheduling Information" -:
Maps=212, Reduces=212, Total Submissions=2, Nodes =106, Map Task Capacity=212 Reduce Task Capacity =212, Avg. Tasks/Node=4.00
Scheduling Information shows -:
Queue Name=default
Guaranteed Capacity Maps (%) :100.0
Guaranteed Capacity Reduces (%) :100.0
Current Capacity Maps : 212
Current Capacity Reduces : 212
User Limit : 25
Reclaim Time limit : 300
Number of Running Maps : 211
Number of Running Reduces : 211
Number of Waiting Maps : 1
Number of Waiting Reduces : 1
Priority Supported : YES
Job Details page displays -:
JobID: job_200810171104_0003 on <jobtracker_hostname>
Kind =map, Num Tasks=212, Pending=0, Running=0, Complete=0, Killed=0, Failed/Killed Task Attempts=0/0
Kind=reduce Num Task=212, Pending=0, Running=0, Complete=0, Killed=0, Failed/Killed Task Attempts=0/0.
This also shows that actually 212 MR tasks are running while queue info displays 211 MR tasks running and 1 in waiting.
Note -: if there are ore then one jobs running queue information display one task than then actual task running
was (Author: karams):
Submitted a job with map and reduce tasks = 212.
When all maps and reduces tasks of job starts running, JobTracker UI displayed following information about "Cluster Summary" and "Scheduling Information" -:
Maps=212, Reduces=212, Total Submissions=2, Nodes =106, Map Task Capacity=212 Reduce Task Capacity =212, Avg. Tasks/Node=4.00
Scheduling Information shows -:
Queue Name=default
Guaranteed Capacity Maps (%) :100.0
Guaranteed Capacity Reduces (%) :100.0
Current Capacity Maps : 212
Current Capacity Reduces : 212
User Limit : 25
Reclaim Time limit : 300
Number of Running Maps : 211
Number of Running Reduces : 211
Number of Waiting Maps : 1
Number of Waiting Reduces : 1
Priority Supported : YES
Job Details page displays -:
JobID: job_200810171104_0003 on gs301308
Kind =map, Num Tasks=212, Pending=0, Running=0, Complete=0, Killed=0, Failed/Killed Task Attempts=0/0
Kind=reduce Num Task=212, Pending=0, Running=0, Complete=0, Killed=0, Failed/Killed Task Attempts=0/0.
This also shows that actually 212 MR tasks are running while queue info displays 211 MR tasks running and 1 in waiting.
Note -: if there are ore then one jobs running queue information display one task than then actual task running
> Scheduling Information for queues shows one map/reduce task less then actual running map/reduce tasks.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4444
> URL: https://issues.apache.org/jira/browse/HADOOP-4444
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Environment: Hadoop r705159, Queue=default, GC=100% MapCapacity=ReduceCapacity=212
> Reporter: Karam Singh
> Assignee: Sreekanth Ramakrishnan
>
> Scheduling Information for queues shows one map/reduce task less then actual running map/reduce tasks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.