dpol1 commented on PR #2183: URL: https://github.com/apache/stormcrawler/pull/2183#issuecomment-5832159722
Had a look at what reaches the fork and what comes back. ConfigMerger drops setSocketTimeoutMillis and setJavaPath: the fork runs java from the PATH with a 60s socket timeout. parse.Content-Type is the raw server header, the tuple metadata overwrites what the fork parsed. The text comes back as one tk:content string reparsed as XML, up to 20M chars twice in the worker. Same root cause for the three: settings go as a JSON file and results as a Map<String,String>, so neither side can check what it gets. Smaller things: the fork starts lazily, so a bad jvmarg makes every URL a parse pipes error; a one-line parse in prepare would fail the bolt instead. PARTIAL_TIMEOUT goes out as a trimmed success while the docs say ERROR, intended? maxfilesperprocess defaults to 10000 on the Tika side. On the heap I'd append -Xmx512m when there's no heap flag, Storm can't give a per-host split. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
