You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sami Siren (JIRA)" <ji...@apache.org> on 2006/07/25 21:40:15 UTC
[jira] Updated: (NUTCH-246) segment size is never as big as topN or
crawlDB size in a distributed deployement
[ http://issues.apache.org/jira/browse/NUTCH-246?page=all ]
Sami Siren updated NUTCH-246:
-----------------------------
Fix Version/s: 0.9-dev
(was: 0.8-dev)
> segment size is never as big as topN or crawlDB size in a distributed deployement
> ---------------------------------------------------------------------------------
>
> Key: NUTCH-246
> URL: http://issues.apache.org/jira/browse/NUTCH-246
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 0.8-dev
> Reporter: Stefan Groschupf
> Priority: Minor
> Fix For: 0.9-dev
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira