Hadoop Common
  1. Hadoop Common
  2. HADOOP-1954

start task tracker and stop task tracker scripts

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: scripts
    • Labels:
      None

      Description

      we should have scripts for starting and stopping just the task tracker

        Activity

        Hide
        Kate Rhodes added a comment -

        a script to start the task tracker and a script to stop it

        Show
        Kate Rhodes added a comment - a script to start the task tracker and a script to stop it
        Hide
        Kate Rhodes added a comment -

        just scripts to start and stop the task tracker

        Show
        Kate Rhodes added a comment - just scripts to start and stop the task tracker
        Hide
        Doug Cutting added a comment -

        This is just 'bin/hadoop-daemon.sh start tasktracker' no? Why do we need a separate script for that? Also, in your patch you use 'hadoop-daemons.sh' (plural) which will run a tasktracker on each slave node, rather than just on the current node.

        Show
        Doug Cutting added a comment - This is just 'bin/hadoop-daemon.sh start tasktracker' no? Why do we need a separate script for that? Also, in your patch you use 'hadoop-daemons.sh' (plural) which will run a tasktracker on each slave node, rather than just on the current node.
        Hide
        Owen O'Malley added a comment -

        This is redundant with bin/hadoop-daemon.sh script.

        Show
        Owen O'Malley added a comment - This is redundant with bin/hadoop-daemon.sh script.
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12366630/start_stop_tt_scripts.patch
        against trunk revision r579928.

        @author +1. The patch does not contain any @author tags.

        javadoc +1. The javadoc tool did not generate any warning messages.

        javac +1. The applied patch does not generate any new compiler warnings.

        findbugs +1. The patch does not introduce any new Findbugs warnings.

        core tests +1. The patch passed core unit tests.

        contrib tests +1. The patch passed contrib unit tests.

        Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/832/testReport/
        Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/832/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/832/artifact/trunk/build/test/checkstyle-errors.html
        Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/832/console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12366630/start_stop_tt_scripts.patch against trunk revision r579928. @author +1. The patch does not contain any @author tags. javadoc +1. The javadoc tool did not generate any warning messages. javac +1. The applied patch does not generate any new compiler warnings. findbugs +1. The patch does not introduce any new Findbugs warnings. core tests +1. The patch passed core unit tests. contrib tests +1. The patch passed contrib unit tests. Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/832/testReport/ Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/832/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/832/artifact/trunk/build/test/checkstyle-errors.html Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/832/console This message is automatically generated.
        Hide
        Kate Rhodes added a comment -

        you're right it should be singular instead of plural to just start it on this node. Why we need it? for the same reason we need any of the simple start stop scripts. To save typing. Plus it makes life easier for newbs like me. There's scripts for starting all the other things but when you're starting out it seems likely than one of the things you're going to be doing is setting up task trackers on nodes. Having a script right there in the bin dir that does it for you helps get you up and running faster and gives new users one less hurdle to get over. It wasn't at all obvious to me how to start just a task tracker.

        These aren't "needed" but they're nice to have, don't really get in the way of anything, and can make life easier for new users before they get frustrated and go away.

        Show
        Kate Rhodes added a comment - you're right it should be singular instead of plural to just start it on this node. Why we need it? for the same reason we need any of the simple start stop scripts. To save typing. Plus it makes life easier for newbs like me. There's scripts for starting all the other things but when you're starting out it seems likely than one of the things you're going to be doing is setting up task trackers on nodes. Having a script right there in the bin dir that does it for you helps get you up and running faster and gives new users one less hurdle to get over. It wasn't at all obvious to me how to start just a task tracker. These aren't "needed" but they're nice to have, don't really get in the way of anything, and can make life easier for new users before they get frustrated and go away.
        Hide
        Kate Rhodes added a comment -

        calls hadoop-daemon.sh instead of hadoop-daemons.sh

        Show
        Kate Rhodes added a comment - calls hadoop-daemon.sh instead of hadoop-daemons.sh
        Hide
        Edward J. Yoon added a comment -

        I think this is a nice to have but not necessary.

        Show
        Edward J. Yoon added a comment - I think this is a nice to have but not necessary.
        Hide
        Nikhil Mulley added a comment -

        My approach to this would be to have a script which knows what are the current task trackers online and connected currently to the JobTracker, should be issued an RPC command, to get restarted. That ways, I can restart all my tasktrackers in my cluster restarted from a single host/place(i.e.,. where the jobtracker is running upon).

        Here is the thing, I would propose:
        have another script named 'mapred-cluster.sh' with the following options.

        mapred-cluster.sh [jobtracker|tasktracker] [options]

        jobtracker start|stop|restart # this would restart only the jobtracker component of the cluster

        tasktracker [-h comma seperated hostnames|ipaddress|all] start|stop|restart # this should based on the argument value provided by -h option, should initiate the action as noted by start|stop|restart. If -h option is not provided, assume it is the localhost. If 'all' is provided as an argument value to the option -h, then it should initiate a (batch?) restart of all the tasktrackers connected to the jobtracker.

        Let me know how does it sound to guys. Anyone willing to code a patch/hookup a jar for this?

        Nikhil

        Show
        Nikhil Mulley added a comment - My approach to this would be to have a script which knows what are the current task trackers online and connected currently to the JobTracker, should be issued an RPC command, to get restarted. That ways, I can restart all my tasktrackers in my cluster restarted from a single host/place(i.e.,. where the jobtracker is running upon). Here is the thing, I would propose: have another script named 'mapred-cluster.sh' with the following options. mapred-cluster.sh [jobtracker|tasktracker] [options] jobtracker start|stop|restart # this would restart only the jobtracker component of the cluster tasktracker [-h comma seperated hostnames|ipaddress|all] start|stop|restart # this should based on the argument value provided by -h option, should initiate the action as noted by start|stop|restart. If -h option is not provided, assume it is the localhost. If 'all' is provided as an argument value to the option -h, then it should initiate a (batch?) restart of all the tasktrackers connected to the jobtracker. Let me know how does it sound to guys. Anyone willing to code a patch/hookup a jar for this? Nikhil

          People

          • Assignee:
            Unassigned
            Reporter:
            Kate Rhodes
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development