allegro / allegro/marathon-consul

Manual trigger of sync

Open
#138 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
200
Forks
33
PR merge metrics
No merged PRs in 30d

Description

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?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.