diff options
| author | Martin Polden <mpolden@mpolden.no> | 2020-10-06 15:05:20 +0200 |
|---|---|---|
| committer | Martin Polden <mpolden@mpolden.no> | 2020-10-06 15:23:41 +0200 |
| commit | 3aedbdfc275fd16081c78b1fee0b95ff8fd0990b (patch) | |
| tree | f7f64547329637dc9572cd08470f8e2cd6fff231 /zkfacade | |
| parent | 32583c92499e91586a39f5744cc65b72bdea0702 (diff) | |
Stop taking config lock exclusively in node-repository
We believe we've identified how locking should behave, at least in the
short-term:
1) Migrate existing use of `/config/v2/locks/<application-id>` inside
node-repository to only use `/provision/v1/locks/<application-id>`. This ensures
that prepare only acquires `/provision/v1/locks/<application-id>` on the
node-repository side. Locks and node repo writes always happen together, i.e.
we're not building a list of transaction that are committed at some later point.
2) Ensure that transactional operations such as `active` and `deactivate` holds
both `/config/v2/locks/<application-id>` and
`/provision/v1/locks/<application-id>` until the transaction is committed.
Diffstat (limited to 'zkfacade')
0 files changed, 0 insertions, 0 deletions