I'm only calling `withSession()` though, i'm not trying to use bookmarks on DBs that dont have repli

I'm only calling

withSession()

withSession()

though, i'm not trying to use bookmarks on DBs that dont have replication enabled, so i cant confirm if that works or not. I imagine it would though

Whitey•4/11/25, 3:27 AM

I'm playing around with CF pages and D1 for a hobby project. Drizzle handles my database migrations and have I the migrations directory set in

wrangler.jsonc

wrangler.jsonc

. I can successfully run the migrations if I do

wrangler d1 migrations apply <database>

wrangler d1 migrations apply <database>

, but when I then do

wrangler pages dev --d1 MY_DB=mydb

wrangler pages dev --d1 MY_DB=mydb

to run my app locally, drizzle complains about a missing table, seemingly my migrations haven't been run after all.

I also noticed after running both commands there are two

.sqlite

.sqlite

files in

.wrangler/state/v3/d1/miniflare-D1DatabaseObject

.wrangler/state/v3/d1/miniflare-D1DatabaseObject

does the
```
migrations apply
```
```
migrations apply
```
command operate on a different local database than
```
wrangler pages dev
```
```
wrangler pages dev
```
? Just trying to figure out the best way to set this up, and feel like I'm using wrangler incorrectly here

Aajgeiss0702 I'm only calling `withSession()` though, i'm not trying to use bookmarks on DBs ...

lambrospetrou•4/11/25, 7:26 AM

Even with using a bookmark, when you turn off replication and eventually all replicas are killed, your queries will go to the primary. The primary has the most up-to-date database since all writes go there so it will always be caught up with the provided bookmark instantly.

Llambrospetrou Even with using a bookmark, when you turn off replication and eventually all rep...

lambrospetrou•4/11/25, 7:32 AM

The way we thought about it is that since the

D1DatabaseSession

D1DatabaseSession

has the same

prepare/batch()

prepare/batch()

methods as the top level D1 Binding your code doing D1 queries should just accept

D1DatabaseSession

D1DatabaseSession

. And therefore you can pass in your code either the top level binding or the session create by

withSession()

withSession()

.

So, switching between always using the top level binding or the session is a single line change. Like I did in https://github.com/cloudflare/templates/blob/c624b31b63568adebcba1b63f600dbc81cf3a5fa/d1-starter-sessions-api-template/src/index.ts#L52

Zack•4/11/25, 9:09 AM

Is someone able to check through the d1 issues I experienced yesterday and see why my database never became healthy after switching to the replicated database instead of 6 individually placed databases?

Zack•4/11/25, 9:14 AM

These were all the errors we experienced from D1, which was most of our cache missed requests. I think a few requests successfully ran, but it was a very low percentage and the database fell over immediately afterwards again

Zack•4/11/25, 10:08 AM

More on the above, tried to slowly roll in the load on the replicated database, which all seemed fine until hitting 75% traffic, which has now caused p80 to rocket and errors to start appearing. Waiting to see if it dies down.

Zack•4/11/25, 10:09 AM

Can someone at cloudflare confirm a suspicion I have? Non-replicated D1 feels like either, the instances (DOs) live for longer before being shutdown or are just faster at starting up? Some of the problem seems to be that a region gets hit where the instance isn't available currently and that causes slowdowns while that replica comes online

ZZack These were all the errors we experienced from D1, which was most of our cache mi...

lambrospetrou•4/11/25, 10:28 AM

The team will be looking your database's errors today.

ZZack Can someone at cloudflare confirm a suspicion I have? Non-replicated D1 feels li...

lambrospetrou•4/11/25, 10:29 AM

Non-replicated D1 feels like either, the instances (DOs) live for longer before being shutdown or are just faster at starting up?

No. Replicas start up in the same way as any other database, and non-replicated databases do not live longer.

Llambrospetrou > Non-replicated D1 feels like either, the instances (DOs) live for longer befor...

Zack•4/11/25, 10:29 AM

Interesting, this behaviour is pretty confusing then

Llambrospetrou The team will be looking your database's errors today.

Zack•4/11/25, 10:29 AM

Thanks, let me know if there's anything you need from me

ZZack Interesting, this behaviour is pretty confusing then

lambrospetrou•4/11/25, 10:30 AM

Some of the problem seems to be that a region gets hit where the instance isn't available currently and that causes slowdowns while that replica comes online

This is true. If you just hit your replication-enabled database from a region for the first time, the replica there will have to start up.

Zack•4/11/25, 10:30 AM

Is it more useful if there is load on the database when they go to look at it, or will they be able to just look at logs and metrics from now and when I tried also yesterday

Llambrospetrou > Some of the problem seems to be that a region gets hit where the instance isn'...

Zack•4/11/25, 10:30 AM

Right, the confusing part to me is that we saw none of this behaviour when running 6 seperate D1 instances located within each region

ZZack Right, the confusing part to me is that we saw none of this behaviour when runni...

lambrospetrou•4/11/25, 10:31 AM

I doubt that, since your normal database would have to start up as well when first queried.

Zack•4/11/25, 10:31 AM

Also, this database has zero writes occurring, it's solely just reads

Llambrospetrou I doubt that, since your normal database would have to start up as well when fir...

Zack•4/11/25, 10:31 AM

I have metrics to prove it

Zack•4/11/25, 10:31 AM

It may not be the startups causing the problem, but we didn't have these problems when running 6 seperate instances

Zack•4/11/25, 10:32 AM

Lets see what the team find when they take a look into it

ZZack It may not be the startups causing the problem, but we didn't have _these_ probl...

lambrospetrou•4/11/25, 10:33 AM

When did you first enable replication for your database?

Zack•4/11/25, 10:34 AM

We have 7 databases, all with the same data. 6 to have one for each region, and the 7th in preperation for read replicas. I turned read replicas on yesterday after the release, and toggled it a couple times to see if that fixed the behaviour.

Zack•4/11/25, 10:34 AM

This instance primary is based in WEUR

Zack•4/11/25, 10:35 AM

This also gives us the ability to switch between the two setups easily with just a worker rollback

Zack•4/11/25, 10:38 AM

But yea, just reverted back to our old setup now, and immediately we return to no errors and latencies return back to normal ranges. Not a single request >2 seconds

Zack•4/11/25, 10:40 AM

ZZack But yea, just reverted back to our old setup now, and immediately we return to n...

lambrospetrou•4/11/25, 10:49 AM

The latency spikes you see is probably because those fail. Anyway, we will check the errors and see what's going on with your database.

gruntlord6•4/11/25, 12:29 PM

With the read replicas being a thing, is it possible for things like the export to not lock up the db?

Or is that not possible due to how the infrastructure is setup?

gruntlord6•4/11/25, 12:29 PM

I know we can work around it by copying to a staging database first but I figured I'd ask

gruntlord6•4/11/25, 1:20 PM

Can't you just revert?

Brayden•4/11/25, 1:23 PM

@Roopendra I've mentioned this to the team just an FYI – sorry you're experiencing this!

Brayden•4/11/25, 1:24 PM

Oh good! Is your database back up now?

Ggruntlord6 With the read replicas being a thing, is it possible for things like the export ...

lambrospetrou•4/11/25, 1:24 PM

That's the plan, but not yet. Locking is still happening at the moment.

lambrospetrou•4/11/25, 1:28 PM

FYI, disabling replicas is not instant. If replicas are created and process some of your queries, it can take a few hours for them to stop processing queries and completely disappear.

Also, if the UI is slow sometimes, you can use the PATCH API directly to manage read replication: https://developers.cloudflare.com/api/resources/d1/subresources/database/methods/edit/

The read replication mode for the database. Use 'auto' to create replicas and allow D1 automatically place them around the world, or 'disabled' to not use any database replicas (it can take a few hours for all replicas to be deleted).

Also, as I mentioned yesterday our recommendation is to first try it in your staging databases or test environments and once verified that it works for your case enable it in production.

Cloudflare API | D1 › Database › Update D1 Database Partially

Interact with Cloudflare's products and services via the Cloudflare API

gruntlord6•4/11/25, 1:46 PM

In general I would not use a beta in prodution unless I have verified its working with test projects

gruntlord6•4/11/25, 1:46 PM

I know its not helpful after the fact, but figured I would mention that

RRoopendra Yeah, my fault.

Brayden•4/11/25, 1:50 PM

I'm adding a beta label to the UI to make it more clear. We should have mentioned it's still in beta in our UI as well.

gruntlord6•4/11/25, 1:59 PM

yea, it was clear in the announcement from what I recall but UI would be nice for those who don't read that diretcly or missed that part

I'm only calling `withSession()` though, i'm not trying to use bookmarks on DBs that dont have repli

Similar Threads