[ https://issues.apache.org/jira/browse/NUTCH-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644825#comment-17644825 ]
Markus Jelsma commented on NUTCH-2978: -------------------------------------- This morning i saw one of our internal projects spewing the same error as any23, it was quickly remedied by upgrading a dependency further down the line. Not sure if this will go as easy with the any23 plugin, i'll take a look Regarding running on Hadoop, I just ran a patched 1.20 CrawldbReader job on a 3.3.4 cluster, i ran flawless! Encouranged by the result i quickly ran a generate, followed by a fetch. The fetch failed due to LinkageError in our parser plugin, similar as parse-tika. Too bad. A local indexchecker runs fine, an indexchecker using a job file fails with the same error. > Move to slf4j2 and remove log4j1 and reload4j > --------------------------------------------- > > Key: NUTCH-2978 > URL: https://issues.apache.org/jira/browse/NUTCH-2978 > Project: Nutch > Issue Type: Task > Reporter: Markus Jelsma > Priority: Major > Attachments: NUTCH-2978.patch > > > I got in trouble upgrading some dependencies and got a lot of LinkageErrors > today, or with a Tika upgrade, disappearing logs. This patch fixes that by > moving to slf4j2, using the corrent log4j2-slfj4-impl2 and getting rid of old > log4j -> reload4j. > > This patch fixes it. -- This message was sent by Atlassian Jira (v8.20.10#820010)