[
https://issues.apache.org/jira/browse/NUTCH-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978902#comment-14978902
]
Aron Ahmadia commented on NUTCH-2132:
-------------------------------------
[~sujenshah] - I'm reviewing this again now. One issue I'm having is that if I
start a Nutch server with this patch and RMQ configured to publish, crawls fail
unless a RMQ server is available.
Since the point of a pub/sub model is that these sort of messages are ephemeral
(and the routing exchanges may go up and down), it should not be a fatal error
for RMQ to go down.
Barring that, is it possible to reconfigure the server using the config REST
endpoint to not publish? Testing now...
> Publisher/Subscriber model for Nutch to emit events
> ----------------------------------------------------
>
> Key: NUTCH-2132
> URL: https://issues.apache.org/jira/browse/NUTCH-2132
> Project: Nutch
> Issue Type: New Feature
> Components: fetcher, REST_api
> Reporter: Sujen Shah
> Labels: memex
> Fix For: 1.12
>
> Attachments: NUTCH-2132.patch, PubSub_routingkey.patch
>
>
> It would be nice to have a Pub/Sub model in Nutch to emit certain events (ex-
> Fetcher events like fetch-start, fetch-end, a fetch report which may contain
> data like outlinks of the current fetched url, score, etc).
> A consumer of this functionality could use this data to generate real time
> visualization and generate statics of the crawl without having to wait for
> the fetch round to finish.
> The REST API could contain an endpoint which would respond with a url to
> which a client could subscribe to get the fetcher events.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
