[
https://issues.apache.org/jira/browse/HADOOP-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712736#action_12712736
]
Hemanth Yamijala commented on HADOOP-5739:
------------------------------------------
Some more comments:
- Change in ClusterWithCapacityScheduler seems unnecessary.
- In the test case, maybe intention is to delete testDir1, instead of testDir.
- Wrap to 80 characters.
- Why check the JobStatus only when the last event is SUCCEEDED. I think we
should check for both. Also didn't understand why this is in a for loop.
- When creating the jobConf, maybe you should use the previously created job
conf in MiniMRCluster.createJobConf
> After JobTracker restart Capacity Schduler does not schedules pending tasks
> from already running tasks.
> --------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5739
> URL: https://issues.apache.org/jira/browse/HADOOP-5739
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.20.0
> Reporter: Karam Singh
> Assignee: rahul k singh
> Attachments: hadoop-5739-3.patch, hadoop-5739-latest.patch,
> hadoop-5739.patch, hadoop-5739.patch
>
>
> After JobTracker restart Capacity Schduler does not schedules pending task
> from already running tasks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
