We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Figure out what needs to be done in the event a waiter is throttled.
Anecdotally, waiting on a throttled batch means you'll wait forever. Having a hard time finding docs references on throttle behavior atm.
If we retry: add connection context & table/column data to the [waiter] object class so we can invoke retry from inside Wait-Xb
[waiter]
Wait-Xb
TODO: resubmit, needs Table & Column data from Start-Cmd AFAICT $NewArchiveCmd = @{ Start = $Waiter.Start End = $Waiter.End } $NewWaiter = Start-XbAsyncArchive @NewArchiveCmd Write-Warning "$(Get-Date -Format o): Re-submitting operation for Start: '$($Waiter.Start)', End: '$($Waiter.End)'. Old OperationId: '$($Waiter.OperationId)', New OperationId: '$($NewWaiter.OperationId)'" $Waiter.OperationId = $NewWaiter.OperationId
If we abort the batch (as in 43a9aa5), what do we do to the queue to ensure we don't get throttled again immediately?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Figure out what needs to be done in the event a waiter is throttled.
Anecdotally, waiting on a throttled batch means you'll wait forever. Having a hard time finding docs references on throttle behavior atm.
If we retry: add connection context & table/column data to the
[waiter]
object class so we can invoke retry from insideWait-Xb
If we abort the batch (as in 43a9aa5), what do we do to the queue to ensure we don't get throttled again immediately?
The text was updated successfully, but these errors were encountered: