Skip to content

Conversation

@tamilmani1989
Copy link
Member

Reason for Change:

Issue Fixed:

Requirements:

Notes:


// Maximum number of retries before failing a lock call.
lockMaxRetries = 200
lockMaxRetries = 100
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how quickly do we retry? this could go by very fast. should there be some exponential back-off, maybe?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't 10 seconds long enough? 100 retries with 100ms delay

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know. Usually (like with http calls), we would do an exponential back-off where we wait maybe twice as long every time instead of a fixed interval (ex: 50ms, 100, 200, 400, 800, ...). But if 100x100ms is what we want, that's fine with me

Co-authored-by: Evan Baker <rbtr@users.noreply.github.com>
@tamilmani1989
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@tamilmani1989 tamilmani1989 merged commit 5882752 into master Sep 30, 2021
@tamilmani1989 tamilmani1989 deleted the tamanoha/lockfix branch October 1, 2021 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants