discourse是通过1panel的容器部署的，并设置了反向代理进行访问。网站主要用于个人知识管理使用，没有开放注册，只有我一人在线。vps性能是10 vCore (ARM64)，16 GB RAM，512 GB NVMe。 discourse日志中频繁出现以下类似错误警告： DistributedMutex(“memoize_lock_post##2f7d40f44a4b0fa66a711ca8f2ff9278fed9fa72”): held for too long, expected max: 1 secs, took an extra 1 secs activesuppo…

This is probably not caused directly by the reverse proxy. For API-created posts, Discourse uses DistributedMemoizer around PostsController#create to avoid duplicate API post creation. That memoizer uses a Redis-backed DistributedMutex with a very short validity time of 1 second. The warning means …

谢谢您的回复。我这个网站主要用于个人知识管理使用，没有开放注册，只有我一人在线。vps性能是10 vCore (ARM64)，16 GB RAM，512 GB NVMe。我觉得性能上应该没问题了。 1、API 请求是否成功，并且只创建了一个帖子？是的，API发帖成功，并且只创建一个帖子。 2、从客户端角度看，API 请求耗时多久？这个应该怎么查询？我不太了解。 3、在 API 发帖期间，CPU、内存、交换空间或磁盘 I/O 是否已饱和？我查看了一下监控记录，API发帖时，以上资源使用未饱和 4、Redis 和 Postgres 是否位于同一容器/主机内，且运行正常？是…

刚才我把ai插件关掉，通过api发帖，日志中没有出现警告。再开启ai插件，重新通过api发帖，日志中也没有出现警告。我再观察测试一下。

Thanks, that extra detail is useful. Since you are running on ARM64, that may be relevant. Discourse’s ARM/aarch64 container support has historically had some special handling compared with x86_64, so I would mention that clearly in the topic title or first post. The AI plugin result is also inter…

我关闭一段时间 discourse ai 看看是否还出现这个警告

目前测试来看，警告日志的出现与是否启用了discourse ai无关

Thanks for testing that. In that case I would not treat the AI plugin as the likely cause. It may just have been a coincidence, or the disable/re-enable cycle may have changed some transient state temporarily. The most useful next thing to capture is probably the request timing and the pattern of …

今日没有进行发帖，日志中也出现了一次警告 DistributedMutex("memoize_lock_post##59c6dac7790176d15fddc068dea5f734b254f591"): held for too long, expected max: 1 secs, took an extra 1 secs activesupport-8.0.5/lib/active_support/broadcast_logger.rb:218:in 'block in ActiveSupport::BroadcastLogger#dispatch' activesupport-8…

以下是两张图片是连续日志，出现这个警告比较频繁了~:rofl: [image] [image]

通过api 发帖日志中频繁出现警告 [image]

Häufige Fehlerwarnungen für DistributedMutex im Protokoll

Unterstützung

sniper756 14. Mai 2026 um 12:11 6

Ich werde Discourse AI für eine Weile deaktivieren, um zu sehen, ob diese Warnung weiterhin auftritt.

Thema		Antworten	Aufrufe
Discourse not using much RAM Self-hosting server-resources	30	1855	8. August 2021
Discourse installation has been getting slower and slower and slower Self-hosting server-resources	36	1866	15. April 2023
Due to extreme load, this is temporarily being shown to everyone... when it's not really the case Self-hosting server-resources	19	1827	21. Juli 2023
Load average ×2 since last upgrade Bug activitypub	5	248	22. Dezember 2025
502 Bad Gateway for only two Topics Self-hosting arm	19	2029	17. November 2022

Häufige Fehlerwarnungen für DistributedMutex im Protokoll

Verwandte Themen