-
Notifications
You must be signed in to change notification settings - Fork 848
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
About poller freq limitation #17018
Comments
We set a floor to ensure that customers didn't accidentally specify too small a value and flood the endpoint with requests. If this is problematic, the only solution is to write your own polling loop and not use |
@tadelesh can you provide a sample or PR for the issue you are seeing? @jhendrixMSFT what is the floor for the time between requests? Can't we use the floor when we're in playback mode and otherwise use a more reasonable value? |
The floor is one second and is baked into the internal poller type. I suppose we could detect if we're running a test and disable the check. |
It's not the cleanest code, but this can be put into a function and re-used I think. We can also look at adding it to the |
Good idea, and generics should make this reusable. |
@jhendrixMSFT Thanks for the solution. |
I found there exists a limit for the LRO polling interval. When I use the test proxy to do the scenario test, it will be hard to work around it for playback and cause the test duration too long. I know the way to handle it is to remove all the redundant polling tries in recording file, but it is not so convenient. I wonder this limit can be removed or any other better solution?
The text was updated successfully, but these errors were encountered: