allegro / allegro/marathon-consul
Manual trigger of sync
未關閉
- 主要語言
- 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 還沒有評估資料。