You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently when complete_multipart_upload takes too long we send headers to show progress to the cluster, to prevent the client from closing the connection. since we send the headers to keep the connection, we can't write new headers (we get error ERR_HTTP_HEADERS_SENT). currently this happens for version-id and encryption. since we only link the file and don't really copy it, complete multipart upload should not take that long. it should only happen in case on problems with the file system that make the command take a lot of time (see #8524). we should decide if we want to remove set_keep_alive_whitespace_interval function, or to fix it in case we want to keep it
original keep alive issue: #6591. this PR was originally added when we copied the parts, and complete multipart upload time was relative to the file size
More information - Screenshots / Logs / Other output
The text was updated successfully, but these errors were encountered:
Environment info
currently when complete_multipart_upload takes too long we send headers to show progress to the cluster, to prevent the client from closing the connection. since we send the headers to keep the connection, we can't write new headers (we get error ERR_HTTP_HEADERS_SENT). currently this happens for version-id and encryption. since we only link the file and don't really copy it, complete multipart upload should not take that long. it should only happen in case on problems with the file system that make the command take a lot of time (see #8524). we should decide if we want to remove set_keep_alive_whitespace_interval function, or to fix it in case we want to keep it
original keep alive issue: #6591. this PR was originally added when we copied the parts, and complete multipart upload time was relative to the file size
More information - Screenshots / Logs / Other output
The text was updated successfully, but these errors were encountered: