Try `wrangler d1 info <dbname>` 😄

Try

wrangler d1 info <dbname>

wrangler d1 info <dbname>

wrangler d1 info <dbname>

wrangler d1 info <dbname>

IIsaac McFadyen Try `wrangler d1 info <dbname>` 😄

TomK•10/30/24, 3:39 AM

There is no location information in the info command.

TomK•10/30/24, 3:40 AM

TomK•10/30/24, 3:40 AM

wrangler 3.83.0

Isaac McFadyenOP•10/30/24, 3:40 AM

If you do wrangler d1 listwrangler d1 list do you see productionproduction as the version?

Isaac McFadyenOP•10/30/24, 3:41 AM

There should be a running_in_regionrunning_in_region field right between the size and read query count... strange that you don't see it

FFlikTeoh https://discord.com/channels/595317990191398933/799437470004412476/1298726326265...

Chaika•10/30/24, 3:55 AM

anything more interesting output if you try info with the --json flag after the name?

FFlikTeoh Nope. I had other db that wasn't using location hint though. Those shows its cur...

Chaika•10/30/24, 3:58 AM

What do you mean "Current regions"? D1 only runs in a single region/location, if you don't specify a location hint it just does it off the requestor's location, and it'll stay there forever

FFlikTeoh Yeah. What I mean is that, other db that was created without location hints, sho...

Chaika•10/30/24, 4:01 AM

hmm I can't reproduce that. If you have a second, try making another with the same location hint? Just trying to understand scope, I'd guess it's a weird one-off issue
The --json option is just returning what the database get endpoint responds with + graphql, so it missing is api being confused/not a specific wrangler thing

TTomK Click to see attachment

Chaika•10/30/24, 4:04 AM

what's the date of creation on that db?

Chaika•10/30/24, 4:05 AM

oop sorry I meant tomk, yea I saw yours, maybe just an issue for dbs created in a specific period

FFlikTeoh Should I create a new profile db? This one also takes 1.5s to 4s on initial conn...

Chaika•10/30/24, 4:07 AM

how much of that is query time?

FFlikTeoh Under 100ms. It's just the connection time is long for every initial request (wh...

Chaika•10/30/24, 4:09 AM

there's going to be some cold start time but shouldn't be that much

Chaika•10/30/24, 4:09 AM

where are you getting the response times from? The D1 Console wouldn't be a good indictator of response time for example, all requests still have to go you -> core -> d1 instance afaik

FFlikTeoh Yeah it was in the 1.5s to 2s range last week. Yesterday it was at 4.4s. Which w...

Chaika•10/30/24, 4:12 AM

it wouldn't go to sleep if it was constantly being accessed, if you're getting 800ms on some subsequent requests that's still pretty high though

FFlikTeoh This was from insights: ``` { "query": "SELECT * FROM profiles WHERE user_id...

Chaika•10/30/24, 4:13 AM

hmm that one's 0.3ms on avg

Chaika•10/30/24, 4:13 AM

800ms is really high if you have smart placement on, possible that it being borked is connected to the api not showing the location though

FFlikTeoh I can't remember the exact location hint I gave when I created that db. But I th...

Chaika•10/30/24, 4:14 AM

with smart placement on, what was the cf-placement response header?

Chaika•10/30/24, 4:20 AM

Smart Placement is currently ignored when making RPC calls. If Smart Placement is enabled for Worker A, and Worker B declares a Service Binding to it, when Worker B calls Worker A via RPC, Worker A will run locally, on the same machine.

Chaika•10/30/24, 4:20 AM

even if it did work if the underlying d1-calling worker was called via rpc the header wouldn't be passed up anyway

Chaika•10/30/24, 4:23 AM

means it's running wherever the original worker is running, which would be a cf location close to the requestor

Chaika•10/30/24, 4:25 AM

essentially yea. Assuming APAC is your location/the location you're calling the worker from. Not 100% sure about normal, still seems a bit high to me, don't understand how you're measuring the ~400-800ms response time though

CChaika what's the date of creation on that db?

TomK•10/30/24, 4:44 AM

2024-06-07T14:23:14.579Z

TomK•10/30/24, 4:49 AM

I noticed that some databases display "running_in_region," while others do not. I suspect that the ones not displaying this might be due to not specifying a location during creation, and the system automatically determined one.

JJames It's absolutely a valid concern and I don't think anyone is arguing that - if yo...

justaname•10/30/24, 5:01 AM

Hey this is kinda off topic for d1 but was just reading through and a question came to my head is their any way of protecting againts a DNS going down. Like i think cloudflare DNS went down a few times before is it just pray it doesnt happen or is their any way around that?

JIYU•10/30/24, 7:12 AM

Is it just me or are these errors bound to happen as long as I'm using D1? I've been getting a lot of these errors yesterday.
(ERROR: Error: D1_ERROR: D1 storage operation exceeded timeout which caused object to be reset. )
Error occured Time JST23:00~23:45

JJIYU Is it just me or are these errors bound to happen as long as I'm using D1? I've ...

TomK•10/30/24, 7:13 AM

You are not alone.

https://www.cloudflarestatus.com/incidents/h5n23gyb4my2

Increase in D1 Errors

naourass•10/30/24, 2:31 PM

I'm trying to apply a migration on a previewpreview db, but the command is failing with Exit Code 1Exit Code 1 without any error message. Any idea what am I doing wrong or what could be the error cause here?

Update: Issue resolved, I had to create an independent preview database and pass its id to preview_database_idpreview_database_id. Note that doing this will change the id of your local database too if any.

Here's my wrangler.tomlwrangler.toml db config:

[[d1_databases]]
binding = "CORE_DB"
database_name = "phoenix-core-prod"
database_id = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
migrations_dir="database/migrations/core"
preview_database_id = "CORE_DB"

[[d1_databases]]
binding = "CORE_DB"
database_name = "phoenix-core-prod"
database_id = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
migrations_dir="database/migrations/core"
preview_database_id = "CORE_DB"

Here's the npmnpm script:
"db:migrate:core:preview": "wrangler d1 migrations apply phoenix-core-prod --remote --preview""db:migrate:core:preview": "wrangler d1 migrations apply phoenix-core-prod --remote --preview"

And here's the command result:

naourass•10/30/24, 2:37 PM

PS. The migration was applied successfully on the local db (

--local

--local

), and I've already created the phoenix-core-prod remote db:

naourass•10/30/24, 2:41 PM

And ofc I'm putting the right db id it's just redacted in the wrangler config above.

Nnaourass And ofc I'm putting the right db id it's just redacted in the wrangler config ab...

Hello, I’m Allie!•10/30/24, 2:50 PM

Note DB IDs(and the rest of your wrangler config) are not secret, as anyone would need access to your account to make use of it

naourass•10/30/24, 3:01 PM

Thanks for the note! Back to the issue, I'm note sure if I should create an independent preview db and pass its id to preview_database_idpreview_database_id. Can anyone confirm?

Try `wrangler d1 info <dbname>` 😄

Similar Threads

Similar Threads

Similar Threads