question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Frequent 408 Timeout errors while uploading multiple images in parallel

See original GitHub issue

Hi all, We are having frequent 408 timeout errors due to which it has become unusable for us.

@google-cloud/storage : “^5.5.0” node: 12-alpine Avg Image Size: ~5MB

We are running 3 docker containers of same application to upload multiple images in parallel. Randomly gcs stucks for >5 minutes and then return 408 Timeout error.

Code

await bucket("bucketName")
      .upload(filename, {
        destination: "testDestination",
        gzip: true,
        metadata: {
          cacheControl: "no-cache"
        },
        resumable: false
      })

We have also tried file.createWriteStream but having same issue.

Error

error while completing job Multiple errors occurred during the request. Please see the `errors` array for complete details.

    1. Request Timeout
    2. <!DOCTYPE html>
<html lang=en>
  <meta charset=utf-8>
  <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
  <title>Error 408 (Request Timeout)!!1</title>
  <style>
    *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}
  </style>
  <a href=//www.google.com/><span id=logo aria-label=Google></span></a>
  <p><b>408.</b> <ins>That’s an error.</ins>
  <p>Your client has taken too long to issue its request.  <ins>That’s all we know.</ins>

We really appreciate any help in this regard. Thanks

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
himanshuteotiacommented, May 26, 2022

@cor1 Can you please tell us how you fix this issue? I am also running into the same issue

2reactions
muhammadbilal87commented, Dec 15, 2020

We have already gone through issue #1281, we were still facing the same problem so we created a new issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How To Fix the HTTP 408 Error (8 Solutions) - Kinsta
HTTP 408 status code communicates that the server did not receive a timely response from the client. Learn multiple ways to fix this...
Read more >
A brand new website interface for an even better experience!
Frequent 408 Timeout errors while uploading multiple images in parallel.
Read more >
Troubleshooting ideas for 408 Request Timeout when ...
I have a user that is getting an HTTP Request Timeout (408) when in the photo albums page uploading multiple images that are...
Read more >
How to Fix a 408 Request Timeout Error - Lifewire
The 408 Request Timeout error means the request you sent to the website server took longer than it was prepared to wait.
Read more >
Error - 408 Request timeout - Accessing Anypoint Monitoring
408 Request timeout can be a sync timeout. This timeout is generally caused by issues where the customer user profile does not have...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found