nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fjodor Vershinin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (NUTCH-1731) Better cmd line parsing for NutchServer
Date Wed, 09 Apr 2014 18:30:17 GMT

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

Fjodor Vershinin edited comment on NUTCH-1731 at 4/9/14 6:29 PM:
-----------------------------------------------------------------

I made some investigations about this issue. 
So, main problem is NutchServer runs every time in other JVM, so, NutchApp.server reference
can't work. We should connect to running NutchServer by using restful API.
I am working on patch now, which removes mandatory keys from NutchServer command, because
it makes application startup much easier. There should be default port and default logging
level, which can be overrided with command line properties.
And if there will be default port, it would be easier to find running nutch server. So we
should decide, which port we use by default. I would propose 8081.


was (Author: fjodor.vershinin):
I made some investigations about this issue. 
So, main problem is NutchServer runs every time in other JVM, so, NutchApp.server reference
can't work. We should connect to running NutchServer by using restful API.
I am working on patch now, which removes mandatory keys from NutchServer command, because
it makes application startup much easier. There should be default port and default logging
level, which can be overrided with command line properties.

> Better cmd line parsing for NutchServer
> ---------------------------------------
>
>                 Key: NUTCH-1731
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1731
>             Project: Nutch
>          Issue Type: Improvement
>          Components: REST_api
>    Affects Versions: 2.2
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 2.3
>
>         Attachments: NUTCH-1731.patch
>
>
> We can't currently stop a running server without killing the job via pid or something
similar.
> A simple switch should be added to permit this.
> All is needs to do is call NutchServer#stop which will check to see if there are running
tasks... if not then gracefully shut down the server instance. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message