Keep worker running without request

I will be streaming files from S3/R2 to another service. I am planning to use worker for this scenario, since it has no bandwidth fee and any other cpu process usage. Is it possible to keep worker streaming files even after i cancel the 'fetch' request? In the docs it says, it can keep running at most 30 secs after fetch cancelled.
I am pretty sure, 30 secs would be enough to deliver the files, since they are a few GBs at most.

Bbajosi I will be streaming files from S3/R2 to another service. I am planning to use wo...

Hello, I’m Allie!•3/5/23, 2:48 PM

Like this?

export default {
  async fetch(req, env, ctx) {
    // get object name/remote url somehow
    ctx.waitUntil(fetch("https://another.service", {
      method: "POST",
      body: (await env.R2.get("object")).body()
    }));
    return new Response();
  }
}

export default {
  async fetch(req, env, ctx) {
    // get object name/remote url somehow
    ctx.waitUntil(fetch("https://another.service", {
      method: "POST",
      body: (await env.R2.get("object")).body()
    }));
    return new Response();
  }
}

bajosiOP•3/5/23, 4:33 PM

would this wait until fetch request is done, or would it stop the worker after 30 secs?

Bbajosi would this wait until fetch request is done, or would it stop the worker after 3...

Hello, I’m Allie!•3/5/23, 5:01 PM

It would stop when you hit the CPU Limits for your plan, or the Worker is automatically evicted by the runtime.

Keep worker running without request

Similar Threads

Similar Threads

Similar Threads