hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4367) mapred job -kill tries to connect to history server
Date Sat, 04 Aug 2012 00:17:02 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428492#comment-13428492
] 

Jason Lowe commented on MAPREDUCE-4367:
---------------------------------------

Yes, it's still happening for me.  From a recent trunk pull on a single-node cluster where
the history server isn't running yet:

{noformat}
$ mapred job -kill job_1344038428359_0002
2012-08-04 00:09:56,871 INFO  mapred.ClientServiceDelegate (ClientServiceDelegate.java:getProxy(255))
- Application state is completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history
server
2012-08-04 00:09:57,886 INFO  ipc.Client (Client.java:handleConnectionFailure(715)) - Retrying
connect to server: includespoke.champ.corp.yahoo.com/10.74.91.112:10020. Already tried 0 time(s);
retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
2012-08-04 00:09:58,887 INFO  ipc.Client (Client.java:handleConnectionFailure(715)) - Retrying
connect to server: includespoke.champ.corp.yahoo.com/10.74.91.112:10020. Already tried 1 time(s);
retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
2012-08-04 00:09:59,890 INFO  ipc.Client (Client.java:handleConnectionFailure(715)) - Retrying
connect to server: includespoke.champ.corp.yahoo.com/10.74.91.112:10020. Already tried 2 time(s);
retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
2012-08-04 00:10:00,891 INFO  ipc.Client (Client.java:handleConnectionFailure(715)) - Retrying
connect to server: includespoke.champ.corp.yahoo.com/10.74.91.112:10020. Already tried 3 time(s);
retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS)
...
{noformat}

And here's what it says after I start the history server:

{noformat}
$ mapred job -kill job_1344038428359_0002
2012-08-04 00:12:52,226 INFO  mapred.ClientServiceDelegate (ClientServiceDelegate.java:getProxy(255))
- Application state is completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history
server
2012-08-04 00:12:53,195 INFO  mapred.ResourceMgrDelegate (ResourceMgrDelegate.java:killApplication(329))
- Killing application application_1344038428359_0002
Killed job job_1344038428359_0002
{noformat}

Note that in both cases it says the application state is completed and is redirecting.  If
the application state is completed, there's no point in redirecting to the history server
if we're trying to kill the application.  Knowing the application state is completed means
we can short-circuit the kill attempt before the redirect.
                
> mapred job -kill tries to connect to history server
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-4367
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4367
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client, mrv2
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>            Priority: Minor
>
> The {{mapred job -kill}} command attempts to connect to the history server, even though
it is unrelated to the process of killing a job.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message