Jira Data Center mail queue grows due to large subscription groups
プラットフォームについて: Data Center - この記事は、Data Center プラットフォームのアトラシアン製品に適用されます。
このナレッジベース記事は製品の Data Center バージョン用に作成されています。Data Center 固有ではない機能の Data Center ナレッジベースは、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
要約
The mail queue increases in spikes, causing delays in email notifications.
環境
Jira Data Center
診断
In atlassian-jira.log, we see messages like these:
2024-08-15 12:00:01,501-0400 Sending mailitem com.atlassian.jira.mail.SubscriptionMailQueueItem id: '100001' owner: 'myuser' INFO anonymous Mail Queue Service [c.a.jira.mail.SubscriptionMailQueueItem] Sending subscription '100001' of filter '123123' to 987 recipients.These messages are logged every time a subscription is triggered for more than 30 recipients.
原因
The mail queue is generally a single-threaded process, so when a large number of messages are added to the queue in ashort time span (almost 1k in the example above), that introduces a delay as Jira now needs to process such a large number of notifications.
This is described also in JRASERVER-61543 - Outgoing Mail Stopped Working due to Large Group Filter Subscription.
ソリューション
回避策:
Go to Administration
> System > Mail Queue and flush the queue.
This will create a new thread and send more messages to the SMTP server in parallel and help alleviate the issue temporarily, until the queue clears.
Definitive solution:
- Search for "Sending subscription" entries in the logs.
- Navigate to the endpoint
/secure/ViewSubscriptions.jspa?filterId=<filter_ID>replacing the <filter_ID> by the filter referenced in the logs (123123 in our example) - When you hover the cursor over the Edit option, notice the subId parameter in the URL. That is the subscription ID mentioned in the logs.
- Either disable the subscription or change the group to a smaller audience.
If none of the proposed solutions work, please check Health Check: Mail Queue