Neither is more correct. It’s certainly cheaper to batch them up on the producer side if you can.

MMatt Silverlock Neither is more correct. It’s certainly cheaper to batch them up on the producer...

How can I batch at producer side, I don't know. Can you please edit this small part of code and resend please.
Suppose I want batch of 10. Then I have to slice 10 elements from my results array and then pass that to message queue and then consume it. Then try on next 10 batch at producer. Am I correct? You're saying that only right?

Bbharatsuthar07 How can I batch at producer side, I don't know. Can you please edit this small p...

Matt SilverlockOP•11/16/23, 11:29 AM

You are already batching by putting the entire result set into the queue as one message vs a loop over each result. I would suggest just trying out what you have - I would not get stuck on optimizing this right now if it works.

bharatsuthar07•11/16/23, 11:39 AM

Okay got it @Matt thanks

Matt SilverlockOP•11/16/23, 3:56 PM

Some updates for @Queues users:

We're working on landing HTTP Pull, which will allow you to poll a queue and consume it from outside of a Worker (or use a Worker in a poll-based flow vs. push-based). This will likely land just before/just after the holidays.
Queue throughput: our major milestone is about 3-5k msg/sec per queue (message size plays a role here), up from the ~400 msg/sec/queue currently

We're also working on landing controls around setting message delays - e.g.

await env.MY_QUEUE.send(msg, { deliveryDelay: 600 })

await env.MY_QUEUE.send(msg, { deliveryDelay: 600 })

on the producer side, and retry delays on the consumer side - e.g.

messages.batch.retryAfter(300)

messages.batch.retryAfter(300)

.retryAfter(seconds: number)

.retryAfter(seconds: number)

on a per-message basis. API not final.

Bringing Queues to GA late Q1/early Q2 next year alongside other scaling and performance improvements.

MMatt Silverlock Some updates for @Queues users: - We're working on landing HTTP Pull, which wil...

steyblind•11/16/23, 4:06 PM

Right now I've rigged data sync's to S3, which fires an object event to a Lambda, which pings a CF Worker to queue a processing job (which pulls from S3).

I'd MUCH RATHER use R2+Queues and avoid AWS altogether.

Is there an equivalent of an 'write event' I could use to populate a queue with messages as data is sync'd to R2 from [insert external platform here] (in this case, Airbyte, https://docs.airbyte.com/integrations/destinations/r2).

Ssteyblind Right now I've rigged data sync's to S3, which fires an object event to a Lambda...

Matt SilverlockOP•11/16/23, 5:14 PM

This is something on the R2 side, but we're also working on R2 Event Notifications - e.g. uploading to R2 via a Signed URL or the S3 API will publish an event to one of your Queues that you can consume.

Tumbzilla•11/16/23, 7:43 PM

set up a queue consumer that's not scaling as much as I'd expect. The queue currently has ~500k messages (max batch size 32), but the consumer is only firing every 5-10 minutes or so, and concurrency is topping out at 20, with long periods of 0 concurrency in between. All consumer invocations are succeeding.

How would I go about diagnosing the cause of this issue?

TTumbzilla set up a queue consumer that's not scaling as much as I'd expect. The queue curr...

Emilio•11/18/23, 1:11 AM

First thing I’d look at is how long the consumer script is taking to finish consuming a batch. For that you go look at the Worker metrics for the relevant script.

cg•11/18/23, 5:21 PM

Hey all! Is there a timeline for LogPush support in Queues?
It's quite hard to diagnose issues in Queues!

Paul Shriner•11/22/23, 4:38 PM

I cannot for the life of me figure out how to access Durable Objects from my consumer. I have been using itty-durable, but that has proven to be out of reach as I need the IRequest object. I would ideally like to use itty-durable, but at this point, just want it to work.

Unsmart•11/22/23, 4:42 PM

There is no request when using queue consumers... only a fetch has a request. You want to use the env which contains all of the bindings. The request also doesnt contain the bindings when in the fetch handler it is in the env parameter which is standard in all handlers.

Paul Shriner•11/22/23, 4:46 PM

Right, so when I try to do an env.DO.get("id"), it says that the id doesn't work. Hold on, let me get the exact error.

Unsmart•11/22/23, 4:47 PM

That is not a valid id... they look something like:

33ba9f42ca7b9084cf895328953209aae9da953df1a8d8f32f3832fe56

33ba9f42ca7b9084cf895328953209aae9da953df1a8d8f32f3832fe56

Unsmart•11/22/23, 4:47 PM

would also need to use

env.DO.idFromString()

env.DO.idFromString()

to transform to a DO id

Unsmart•11/22/23, 4:48 PM

or env.DO.idFromName

Paul Shriner•11/22/23, 4:48 PM

true

Paul Shriner•11/22/23, 4:48 PM

let userid = this.env.USER.idFromName(uid)
let user = this.env.USER.get(userid);
console.log(user)

Paul Shriner•11/22/23, 4:49 PM

sorry, I was shorthanding, and shouldn't have

Unsmart•11/22/23, 4:50 PM

I'd imagine you probably dont want

this.

this.

should just be

env.

env.

. But whats the error if thats what you have?

Unsmart•11/22/23, 4:53 PM

Example:

export default {
    async queue(batch: MessageBatch<any>, env: Bindings, ctx: ExecutionContext) {
        const stub = env.TestDO.get(env.TestDO.idFromName('1'))
        
        const response = await stub.fetch('https://fake-host/', {})
    }
}

export default {
    async queue(batch: MessageBatch<any>, env: Bindings, ctx: ExecutionContext) {
        const stub = env.TestDO.get(env.TestDO.idFromName('1'))
        
        const response = await stub.fetch('https://fake-host/', {})
    }
}

Paul Shriner•11/22/23, 5:01 PM

When I call

let userid = this.env.USER.idFromName(uid)
let user = this.env.USER.get(userid);    
let brand = await user.GetBrand()

let userid = this.env.USER.idFromName(uid)
let user = this.env.USER.get(userid);    
let brand = await user.GetBrand()

it says that the method GetBrand cannot be found that I would like to call for data access.

when I call

let userid = this.env.USER.idFromString(uid)
let user = this.env.USER.get(userid); 
let brand = await user.GetBrand()

let userid = this.env.USER.idFromString(uid)
let user = this.env.USER.get(userid); 
let brand = await user.GetBrand()

This is the error code on the second:

Invalid Durable Object ID. Durable Object IDs must be 64 hex digits.

In both cases, the uid="GF5ZNCEJLV2X4UQ5FPMAPU6ZNRQ7OXOY3JPT6OOKUDRDEGKJX35TA2Y774"

Paul Shriner•11/22/23, 5:01 PM

Granted, in my non-consumer codes, I am using itty-durable and itty router, which it seems is not available here.

Unsmart•11/22/23, 5:11 PM

GetBrand is not a valid thing on durable objects you can only do fetch calls. An RPC like API is in the works though that would allow direct function calls.

Paul Shriner•11/22/23, 5:12 PM

Ahh, that makes sense. I can hit those methods with itty Durable, but not this way.

Paul Shriner•11/22/23, 5:16 PM

When I print out the user

console.log(JSON.stringify(user))

console.log(JSON.stringify(user))

It return an unpopulated object.

Paul Shriner•11/22/23, 5:19 PM

I will just pour through the itty-code and figure out what I can, I will post back what I figure out in case anyone else runs into this.

MMatt Silverlock Some updates for @Queues users: - We're working on landing HTTP Pull, which wil...

switz•11/22/23, 7:04 PM

huge!! very much waiting for this feature, will get me off SQS entirely.

switz•11/22/23, 7:04 PM

and subsequently off s3

quambo•11/22/23, 10:23 PM

Does

unstable_dev

unstable_dev

work with queues? I've got 2 workers locally, one setup as consumer, one as producer. When the producer sends into the queue, the consumer does not react. Is this supposed to work in local dev?

Qquambo Does `unstable_dev` work with queues? I've got 2 workers locally, one setup as c...

quambo•11/22/23, 10:35 PM

Doesnt work as it seems, from Docs:
Wrangler does not yet support running separate producer and consumer Workers bound to the same Queue locally. To develop locally with Queues, you can temporarily put your consumer’s queue() handler in the same Worker as your producer, so the same Worker acts as both a producer and consumer.

PPaul Shriner I will just pour through the itty-code and figure out what I can, I will post b...

Paul Shriner•11/23/23, 5:16 AM

OK, got it. And the solution was itty-durable related, so...

If you are using the consumer of the queue, and are trying to pull a DO without using itty-router. This is how I solved it.

I used the proxyDurable class which isn't well documented as of writing this. The key though was not to just pass in the binding, but to also pass in the name of the binding in the options argument.

My binding was called "USER", so I would access it by env.USER which is the primary argument in proxyDurable.

let user = proxyDurable(this.env.USER, { name: "USER", parse: true })

let user = proxyDurable(this.env.USER, { name: "USER", parse: true })

then allows me to call the specific DO that I am looking for.

user.get(uid)

user.get(uid)

cg•11/23/23, 6:13 PM

Are Queues down at the moment, I'm seeing

Service Temporarily Unavailable

Service Temporarily Unavailable

cg•11/23/23, 6:13 PM

Is there a Queues status page I can check?

Ccg Are Queues down at the moment, I'm seeing `Service Temporarily Unavailable`

Matt SilverlockOP•11/23/23, 7:23 PM

Can you expand how you’re getting this error? I don’t see any service wide issues.

cg•11/23/23, 7:25 PM

From within a worker, I'm invoking

sendBatch

sendBatch

. This error is being logged to my 3rd party logging infra

cg•11/23/23, 7:26 PM

The pattern here is that the consumer is calling sendBatch to process the next "page" of data

cg•11/23/23, 7:26 PM

as to avoid the 1000 sub request limit

TTom Hi, I'm getting an error on a dead-letter queue consumer that I am unable to ex...

Matt SilverlockOP•11/23/23, 7:29 PM

We suspect this is a bug between the content-type option & DLQs.

Ccg From within a worker, I'm invoking `sendBatch` . This error is being logged to m...

Matt SilverlockOP•11/23/23, 7:29 PM

Can you share your account ID? (it’s safe to share here)

cg•11/23/23, 7:29 PM

Sure, give me a sec

cg•11/23/23, 7:30 PM

Account ID:

10331f908d1d8a668c229d6e85654c7f

10331f908d1d8a668c229d6e85654c7f

Ccg Sure, give me a sec

Matt SilverlockOP•11/23/23, 7:30 PM

I also assume you don’t have a huge backlog?

cg•11/23/23, 7:30 PM

I cleared out the backlog last night

cg•11/23/23, 7:30 PM

Was sitting at like 250k that were just sitting there, so I uh programatically ack'd them all

cg•11/23/23, 7:38 PM

I've submitted a ticket and also reached out to our contact Dylan

Ccg Was sitting at like 250k that were just sitting there, so I uh programatically a...

Matt SilverlockOP•11/23/23, 7:39 PM

Got it. I don't see anything obvious here from a quick look at the metrics.

cg•11/23/23, 7:40 PM

As a FYI, I do have the max_message_batch size as 1, because I've found that if it's too high and one worker handles like 10 messages that each make 100 requests, then the queue just dies (somewhat random and silently) due to the max req limit

cg•11/23/23, 7:40 PM

I'm not sure that has anything to do with this however

Ccg As a FYI, I do have the max_message_batch size as 1, because I've found that if ...

Matt SilverlockOP•11/23/23, 7:42 PM

which queue ID is it? You have two.

8a6de0

8a6de0

89a515

89a515

export default { async queue(batch: MessageBatch<any>, env: Bindings, ctx: ExecutionContext) { const stub = env.TestDO.get(env.TestDO.idFromName('1')) const response = await stub.fetch('https://fake-host/', {}) } }

Neither is more correct. It’s certainly cheaper to batch them up on the producer side if you can.

Similar Threads