You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Lewis John McGibbney (Jira)" <ji...@apache.org> on 2022/01/04 05:12:00 UTC

[jira] [Comment Edited] (NUTCH-2923) Add Job Id in Job Failure messages

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

Lewis John McGibbney edited comment on NUTCH-2923 at 1/4/22, 5:11 AM:
----------------------------------------------------------------------

Yes it absolutely would. I didn't see that when I was browsing the Javadoc on the bus (y)
Absolutely no need to apologize. A patch would be great whenever you can. Thank you


was (Author: lewismc):
Yes it absolutely would. I didn't see that when I was browsing the Javadoc on the bus (y)

> Add Job Id in Job Failure messages
> ----------------------------------
>
>                 Key: NUTCH-2923
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2923
>             Project: Nutch
>          Issue Type: Improvement
>          Components: crawldb, fetcher, generator, injector
>            Reporter: Prakhar Chaube
>            Priority: Minor
>
> In Job classes in case job doesn't succeed a failure message is initialized as follows:
> _String message = "Generator job did not succeed, job status:"_
>               _+ job.getStatus().getState() + ", reason: "_
>               _+ job.getStatus().getFailureInfo();_
> However, this message doesn't contain JobId which can make it really hard to reach the exact job from the logs. Adding JodId to this message will make it easier to track and locate for debugging.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)