-
Notifications
You must be signed in to change notification settings - Fork 223
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
Resolving 500 server timeouts on append blob appends #2430
Conversation
@@ -68,14 +68,18 @@ func (u *appendBlobUploader) GenerateUploadFunc(id common.ChunkID, blockIndex in | |||
u.jptm.LogChunkStatus(id, common.EWaitReason.Body()) | |||
body := newPacedRequestBody(u.jptm.Context(), reader, u.pacer) | |||
offset := id.OffsetInFile() | |||
_, err := u.destAppendBlobClient.AppendBlock(u.jptm.Context(), body, | |||
var timeoutFromCtx bool | |||
ctx := withTimeoutNotification(u.jptm.Context(), &timeoutFromCtx) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need context with timeout here, in older code its different right ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is actually a notifier that a 500 status code was returned during the append block retries so we can check below. This is not adding a request timeout
Tested GCP manually since pipeline GCP creds are not working