[
https://issues.apache.org/jira/browse/NUTCH-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483003
]
Michael Gillis commented on NUTCH-246:
--------------------------------------
I don't see any commit on this issue -- is it actually fixed in 0.9? It looks
resolved, but it's months old. Just curious, thanks
> segment size is never as big as topN or crawlDB size in a distributed
> deployement
> ---------------------------------------------------------------------------------
>
> Key: NUTCH-246
> URL: https://issues.apache.org/jira/browse/NUTCH-246
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Stefan Groschupf
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: injectWithCurTime.patch, injectWithCurTimeMapper.patch
>
>
> I didn't reopen NUTCH-136 since it is may related to the hadoop split.
> I tested this on two different deployement (with 10 ttrackers + 1 jobtracker
> and 9 ttracks and 1 jobtracker).
> Defining map and reduce task number in a mapred-default.xml does not solve
> the problem. (is in nutch/conf on all boxes)
> We verified that it is not a problem of maximum urls per hosts and also not
> a problem of the url filter.
> Looks like the first job of the Generator (Selector) already got to less
> entries to process.
> May be this is somehow releasted to split generation or configuration inside
> the distributed jobtracker since it runs in a different jvm as the jobclient.
> However we was not able to find the source for this problem.
> I think that should be fixed before publishing a nutch 0.8.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
