allegro / allegro/marathon-consul

Manual trigger of sync

未关闭
#138 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Go
星标
200
派生
33
PR 合并指标
30 天内没有已合并 PR

描述

Expose endpoint for triggering sync. Operator should be able to execute sync manually when he notices differences between Marathon and Consul states to resolve the issue faster.

Differences may occur e.g. when marathon-consul doesn't receive events from Marathon.

Things to consider:
- usability: when running multiple instances of marathon-consul as a cluster how to know which instance to call? Currently sync may be executed on the leader only.
- safety: would it be safe if manual sync and scheduled sync were running simultaneously? If not, how to introduce mutual exclusion?

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

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