[
https://issues.apache.org/jira/browse/NUTCH-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770831#comment-17770831
]
Sebastian Nagel commented on NUTCH-1635:
----------------------------------------
Hi [~markus17], did this continue to happen in the last years? Esp., after
upgrading the MapReduce API (NUTCH-2375).
> New crawldb sometimes ends up in current
> ----------------------------------------
>
> Key: NUTCH-1635
> URL: https://issues.apache.org/jira/browse/NUTCH-1635
> Project: Nutch
> Issue Type: Bug
> Affects Versions: 1.7
> Reporter: Markus Jelsma
> Priority: Major
>
> In some weird cases the newly created crawldb by updatedb ends up in
> crawl/crawldb/current/<NUMBER>/. So instead of replacing current/, it ends up
> inside current/! This causes the generator to fail.
> It's impossible to reliably reproduce the problem. It only happened a couple
> of times in the last few years.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
