Spam from Google FeedFetcher requests cause CPU spike

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

When JIRA server is open for public, JIRA threads has reached 100%, CPU usage spike at 90% - 100% and become unaccessible.

A lot of the following appears in the atlassian-jira-http-access.log:

1 2 "GET https://jira.atlassian.com/issues/ HTTP/1.1" - - - - "Feedfetcher-Google; (+http://www.google.com/feedfetcher.html; feed-id=xxxxxx)" "GET https://jira.atlassian.com/issues/ HTTP/1.1" 200 xxx xxx - "Feedfetcher-Google; (+http://www.google.com/feedfetcher.html; feed-id=xxxxxxx)"

Cause

The problem was one user had configured a Chrome plugin for RSS with the url of his/her filter (/issues/?filter=nnnnn). This plugin on the browser provoked requests from FeedFetcher-Google.

Resolution

  • Block the requests on Proxy or Web server.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.