dpol1 opened a new issue, #2058: URL: https://github.com/apache/stormcrawler/issues/2058
When a URL waits in the queue longer than fetcher.timeout.queue, FetcherThread just logs and moves on: no status, no metric, tuple acked. The comment assumes the tuple already failed at Storm level, but that's only true if topology.message.timeout.secs is shorter — otherwise the URL vanishes and the status index never hears about it. Emit FETCH_ERROR? At least a metric? Noticed while planning the characterization tests for #2057 — those will pin the current behaviour for now, the fix would be its own PR. -- 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]
