Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constant PrimaryStatusCheckRetryIntervalInMillis causes potential delay of 512 ms before calling RunAsync on primary replica #244

Open
LeroyK opened this issue Apr 26, 2020 · 1 comment

Comments

@LeroyK
Copy link

LeroyK commented Apr 26, 2020

Before a primary replica's RunAsync is called, StatefulServiceReplicaAdapter waits for the partition to become writable. This is currently done at a fixed interval of 512 ms, which could result in a delay of 512 ms for RunAsync to run on a primary replica. For applications that require fast primary replica switches, this is undesirable.

await Task.Delay(PrimaryStatusCheckRetryIntervalInMillis, cancellationToken);

I would like to suggest making this value configurable instead of a constant of more than half a second.

@LeroyK
Copy link
Author

LeroyK commented Nov 20, 2020

Is there any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants