hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3695) [HOD] Have an ability to run multiple slaves per node
Date Sun, 06 Jul 2008 06:34:46 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610722#action_12610722

Hemanth Yamijala commented on HADOOP-3695:

Looks good. Minor points:

- In bin/hod, there is a check that tries to make sure ringmaster.workers_per_ring is atleast
1. But the check is incorrect, as it checks for an error condition with value <= 1, rather
than < 1.
- Small formatting errors where workers_per_ring is defined bin/hod and bin/ringmaster files.
- While most of the local file system directories are generated with different names for the
different workers, the mapred system directory is the same. We just need to make sure (with
someone from the Map/Reduce team) that if tasktrackers from the same host use this system
directory, there are no problems. 
- logcondense.py needs to be enhanced. It now assumes that log file names will only have patterns
like 0-datanode, 0-tasktracker or 1-tasktracker. In general, this can be [number]-datanode
and [number]-tasktracker with this patch.
- We can enhance test cases in testRingmasterRPCs
- We should enhance documentation in the config guide.

> [HOD] Have an ability to run multiple slaves per node
> -----------------------------------------------------
>                 Key: HADOOP-3695
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3695
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: contrib/hod
>            Reporter: Hemanth Yamijala
>            Assignee: Vinod Kumar Vavilapalli
>             Fix For: 0.19.0
>         Attachments: patch_multiple_workers_1.txt
> Currently HOD launches at most one slave per node. For purposes of testing a large number
of slaves on much fewer resources - for e.g. testing scalability of clusters, it will be useful
if it can provision multiple slaves per node.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message