Archetypes' http.content.limit cuts sitemaps, which then fail to parse

未关闭
  • 哪里不对？
#2,305 3 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@dpol1 已经在做这个了。

开始于 2026年11月6日。

评估

这个 Issue 还没有评估数据。

描述

bug

The archetypes set sitemap.discovery: true and http.content.limit: 65536, and the limit applies to sitemaps too. An XML sitemap above 64 KiB is cut and fails to parse, so none of its URLs are discovered. SiteMapParserBolt marks the fetch as FETCH_ERROR and removes isSitemap, so the retry treats it as a page. sitemaps.org allows up to 50 MB.

In a 12-minute crawl of GQ32K hosts, there were 1,457 sitemap parsing failures, all on responses cut at the limit. rzo1 got 4,183 such errors in #2268. The 3.7.0 archetypes have the same settings, and there the fetch ends as ERROR. This affects the configuration shipped with the archetypes. crawler-default.yaml leaves the content size unlimited.

A higher limit in the archetypes would also apply to pages, so I suggest a separate limit for sitemaps, as we have with http.robots.content.limit and as Nutch has with sitemap.size.max. The robots.txt limit goes through the per-URL http.content.limit metadata. Sitemaps found in robots.txt or in a sitemap index already carry isSitemap=true before their fetch, so a sitemap limit could work the same way. A redirect target doesn't carry it, and neither does the retry after a parsing failure, so the limit would have to cover those too.

主要语言
Java
星标
1k
派生
297
平均合并
1 天 11 小时
30 天内合并 PR
61

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

apache/stormcrawler 的其他 Issue

查看 apache/stormcrawler 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。