The scheduler synchronizes metrics periodically. If multiple worker nodes were to run Goloom (future scaling), there is no distributed locking mechanism in the current store implementation to prevent concurrent sync jobs for the same account, which could lead to duplicate or inconsistent analytics data. Suggest implementing a light-weight row-level locking or a dedicated sync-lock table.
The scheduler synchronizes metrics periodically. If multiple worker nodes were to run Goloom (future scaling), there is no distributed locking mechanism in the current store implementation to prevent concurrent sync jobs for the same account, which could lead to duplicate or inconsistent analytics data. Suggest implementing a light-weight row-level locking or a dedicated sync-lock table.
The scheduler synchronizes metrics periodically. If multiple worker nodes were to run Goloom (future scaling), there is no distributed locking mechanism in the current store implementation to prevent concurrent sync jobs for the same account, which could lead to duplicate or inconsistent analytics data. Suggest implementing a light-weight row-level locking or a dedicated sync-lock table.
500
Internal server error
Forgejo version: 17.0.1+gitea-1.22.0