Skip to content

Conversation

@mcrnic
Copy link
Collaborator

@mcrnic mcrnic commented Jan 12, 2026

We used to only check if the move operation happened if we retried. With multiple regions which can retry independently, detecting if we retried from client becomes unreliable.
In this change we relax the idempotency check to succeed if the requrested operation succeeded and the creation time of the new edge is "close enough" to current time. Currently close enough is 1 minute.

Previously if 2 clients tried to move the same file to the same target concurrently, one would succeed and the other would get edge not found. With this change, both may succeed if they are close enough in time.

We used to only check if the move operation happened if we retried.
With multiple regions which can retry independently, detecting if we
retried from client becomes unreliable.
In this change we relax the idempotency check to succeed if the requrested
operation succeeded and the creation time of the new edge is "close enough"
to current time. Currently close enough is 1 minute.

Previously if 2 clients tried to move the same file to the same target
concurrently, one would succeed and the other would get edge not found.
With this change, both may succeed if they are close enough in time.
@mcrnic mcrnic added the ci If given to a PR, the PR will run CI checks. label Jan 12, 2026
@mcrnic mcrnic marked this pull request as ready for review January 12, 2026 13:46
@mcrnic mcrnic merged commit e21416b into main Jan 12, 2026
8 of 9 checks passed
@mcrnic mcrnic deleted the kmod_move_idempotency branch January 12, 2026 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci If given to a PR, the PR will run CI checks.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants