nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Otis Gospodnetic (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (NUTCH-628) Host database to keep track of host-level information
Date Thu, 17 Apr 2008 20:39:22 GMT

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

otis edited comment on NUTCH-628 at 4/17/08 1:37 PM:
-----------------------------------------------------------------

Enis' DomainStatistics tool from NUTCH-439.
(not a solution to this issue, just something that may go well with it)

Here is example usage, for anyone who wants to try DomainStatistics (works nicely):

$ bin/nutch org.apache.nutch.util.domain.DomainStatistics
hdfs://nn:9000/user/otis/crawl/crawldb/current
hdfs://nn:9000/user/otis/ds-host host 8

You can then -cat ds-host file from DFS and pipe it to sort -nrk1 for sorting by count, higher
count first.


      was (Author: otis):
    Enis' DomainStatistics tool from NUTCH-439.
(not a solution to this issue, just something that may go well with it)

  
> Host database to keep track of host-level information
> -----------------------------------------------------
>
>                 Key: NUTCH-628
>                 URL: https://issues.apache.org/jira/browse/NUTCH-628
>             Project: Nutch
>          Issue Type: New Feature
>          Components: fetcher, generator
>            Reporter: Otis Gospodnetic
>         Attachments: NUTCH-628-DomainStatistics.patch, NUTCH-628-HostDb.patch
>
>
> Nutch would benefit from having a DB with per-host/domain/TLD information.  For instance,
Nutch could detect hosts that are timing out, store information about that in this DB.  Segment/fetchlist
Generator could then skip such hosts, so they don't slow down the fetch job.  Another good
use for such a DB is keeping track of various host scores, e.g. spam score.
> From the recent thread on nutch-user@lucene:
> Otis asked:
> > While we are at it, how would one go about implementing this DB, as far as its structures
go?
> Andrzej said:
> The easiest I can imagine is to use something like <Text, MapWritable>.
> This way you could store arbitrary information under arbitrary keys.
> I.e. a single database then could keep track of aggregate statistics at
> different levels, e.g. TLD, domain, host, ip range, etc. The basic set
> of statistics could consist of a few predefined gauges, totals and averages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message