I keep getting " not_entitled [code: 10000]" even though I can connect to the db via datagrip just f

I keep getting " not_entitled [code: 10000]" even though I can connect to the db via datagrip just fine. Do I need to create a token permission for hyperdrive or do I need a paid workers plan? It logs me into cloudflare via oauth so I dont know what I'm not entitled for

Mmeai1 I keep getting " not_entitled [code: 10000]" even though I can connect to the db...

Cyb3r-Jak3•10/10/23, 2:53 PM

Workers paid plan is required for hyperdrive

meai1OP•10/10/23, 2:53 PM

oh okay, thank you

alex (he/him)•10/11/23, 6:39 PM

if hyperdrive keeps connections in a warm pool, does that mean that serverless dbs e.g. neon wouldn't suspend to not pay for compute?

Unsmart•10/11/23, 6:41 PM

If they charge by connection hours then I would assume that would be the case yes

kian•10/11/23, 6:41 PM

There's an initial connection timeout of 15 seconds and an idle connection timeout of 10 minutes.

kian•10/11/23, 6:42 PM

Neon's default auto-suspend delay is 5 minutes

kian•10/11/23, 6:42 PM

I imagine Hyperdrive might let you configure the timeout periods down the line

alex (he/him)•10/11/23, 6:42 PM

Ok that means neon will stay online 10 minutes instead of the 5 minutes?

alex (he/him)•10/11/23, 6:42 PM

Or are idle connection not forcing the db to stay online?

Colin•10/11/23, 10:52 PM

hey y'all - wanted to ask if anyone had opinions regarding Neon w/ Neon's connection pooling vs Neon w/ Hyperdrive (aside from the "one is GA and one isn't")

Colin•10/11/23, 10:53 PM

It seems like the main Hyperdrive-specific features are query caching + analytics (not yet but soon)

Colin•10/11/23, 10:54 PM

does anyone have experience with it / have any thoughts i might be missing?

CColin hey y'all - wanted to ask if anyone had opinions regarding Neon w/ Neon's connec...

Isaac McFadyen•10/11/23, 10:55 PM

Hyperdrive will be more efficient. The reason for that is:

Hyperdrive:
Worker --(very low latency)--> Hyperdrive --(persistent connection)--> Neon, so connection establishment from Worker to Hyperdrive is fast
Neon:
Worker --(higher latency)--> Neon Pooler, so while Neon might handle connection pooling the connections will still take a longer amount of time to start

Workers are rapidly spun up/down based on requests, so initial connection time is very important.

Isaac McFadyen•10/11/23, 10:56 PM

However, your Neon DB might not sleep very well with inactivity on Hyperdrive. See the conversation above.

IIsaac McFadyen Hyperdrive will be more efficient. The reason for that is: **Hyperdrive:** Work...

Colin•10/11/23, 10:58 PM

I definitely understand this for the

pg

pg

driver, but if we're using

@neondatabase/serverless

@neondatabase/serverless

or similar I'd expect their optimizations to reduce round trips would make it closer at least

Colin•10/11/23, 10:59 PM

i'm not sure how close that'd be to hyperdrive, if it's comparable at all

CColin I definitely understand this for the `pg` driver, but if we're using `@neondatab...

Isaac McFadyen•10/11/23, 10:59 PM

Ah - missed that you were using the Serverless driver. That should be fast to start since it's Websockets to the closest Neon node which then uses a long-lived TCP connection.

Isaac McFadyen•10/11/23, 11:01 PM

Check out https://neon.tech/demos/ping-thing if you want some preliminary numbers.

Ping Thing

A @neondatabase/serverless demo

Isaac McFadyen•10/11/23, 11:01 PM

In particular you want the Seconds field.

Colin•10/11/23, 11:03 PM

yep I totally forgot to mention the serverless driver, my bad. so probably a better way to phrase what I was asking about is "how should we expect hyperdrive w/ standard SQL drivers to perform in comparison to neon w/ serverless drivers"

Colin•10/11/23, 11:04 PM

it still seems like Hyperdrive might be faster as it's much closer to the worker despite having more round trips when establishing a connection(?)

Colin•10/11/23, 11:05 PM

but it seems like there's a lot of Neon fans in here who might've tried this instead of just me theorizing

CColin it still seems like Hyperdrive might be faster as it's much closer to the worker...

Matt Silverlock•10/12/23, 10:39 AM

The Neon Serverless driver still needs to make 3-4 round trips for almost every Workers invocation.

CColin but it seems like there's a lot of Neon fans in here who might've tried this ins...

Matt Silverlock•10/12/23, 10:40 AM

CColin but it seems like there's a lot of Neon fans in here who might've tried this ins...

Matt Silverlock•10/12/23, 10:41 AM

This isn’t Neon’s fault: their driver is great in lieu of other options in many serverless environments, but Hyperdrive exists because that’s still not good enough to get latency down.

MMatt Silverlock The Neon Serverless driver still needs to make 3-4 round trips for almost every ...

Isaac McFadyen•10/12/23, 8:40 PM

Question: how is this the case with Websockets? Is there still a handshake procedure that requires extra round-trips?

IIsaac McFadyen Question: how is this the case with Websockets? Is there still a handshake proce...

Matt Silverlock•10/12/23, 8:42 PM

TLS, then WebSocket. Every time.

MMatt Silverlock TLS, then WebSocket. Every time.

Isaac McFadyen•10/12/23, 8:42 PM

Do they not have edge nodes handling TLS closer to the Worker?

IIsaac McFadyen Do they not have edge nodes handling TLS closer to the Worker?

Matt Silverlock•10/12/23, 8:42 PM

No.

Isaac McFadyen•10/12/23, 8:42 PM

I know Prisma has many edge nodes despite having the DB be central.

Isaac McFadyen•10/12/23, 8:43 PM

Oh, interesting. OK then.

IIsaac McFadyen I know Prisma has many edge nodes despite having the DB be central.

Hello, I’m Allie!•10/13/23, 5:13 AM

Isn’t Prisma Edge CF already?

Colin•10/15/23, 11:23 PM

Hi! I'm getting a

Connection terminated unexpectedly

Connection terminated unexpectedly

error thrown while trying to query my Postgres DB w/ Hyperdrive. Using almost exactly the example code here:

const client = new Client({
  connectionString: context.env.DB_HYPERDRIVE.connectionString,
});

// Connect to our database
console.log("START CONNECT");
await client.connect();
console.log("END CONNECT");

// Test query
console.log("START QUERY");
const result = await client.query({
    text: "SELECT * FROM pg_tables",
});
console.log("END QUERY");

// Returns result rows as JSON
return context.json({ result: result });

const client = new Client({
  connectionString: context.env.DB_HYPERDRIVE.connectionString,
});

// Connect to our database
console.log("START CONNECT");
await client.connect();
console.log("END CONNECT");

// Test query
console.log("START QUERY");
const result = await client.query({
    text: "SELECT * FROM pg_tables",
});
console.log("END QUERY");

// Returns result rows as JSON
return context.json({ result: result });

client.connect()

client.connect()

is finishing fine, but

client.query()

client.query()

is throwing

Connection terminated unexpectedly

Connection terminated unexpectedly

. I'm setting

node_compat = true

node_compat = true

in my

wrangler.toml

wrangler.toml

as well. Any ideas?

Colin•10/16/23, 1:54 AM

^^ update, I figured out what this was. I'm connecting to an AWS RDS instance. We had our certificate set to

rds-ca-rsa2048-g1

rds-ca-rsa2048-g1

, the issue fixed itself when changing back to the default

rds-ca-2019

rds-ca-2019

. Definitely a confusing error message (not sure if this is a

pg

pg

issue, or a Workers issue via the

connect

connect

call), but hopefully this can help someone else!

CColin ^^ update, I figured out what this was. I'm connecting to an AWS RDS instance. W...

Matt Silverlock•10/16/23, 10:12 AM

This is because Hyperdrive doesn’t yet support custom CAs, and the “newer” AWS CA requires the client (Hyperdrive) to have it in its trust store.

CColin ^^ update, I figured out what this was. I'm connecting to an AWS RDS instance. W...

Matt Silverlock•10/16/23, 2:02 PM

For clarity, after re-reading your message: this is via Hyperdrive, right? Not just

connect()

connect()

directly?

MMatt Silverlock This is because Hyperdrive doesn’t yet support custom CAs, and the “newer” AWS C...

Colin•10/16/23, 2:05 PM

I'm a little bit confused here. The docs do call out custom CA certs, but the default mode in

pg

pg

(not sure what Hyperdrive->AWS is using) doesn't verify certificates

MMatt Silverlock For clarity, after re-reading your message: this is via Hyperdrive, right? Not j...

Colin•10/16/23, 2:05 PM

Correct.

connect()

connect()

directly w/

sslmode=REQUIRE

sslmode=REQUIRE

doesn't verify the certs, so it works as expected

Colin•10/16/23, 2:05 PM

It's only when connecting via Hyperdrive, which I'm assuming is verify-ca or verify-full

CColin It's only when connecting via Hyperdrive, which I'm assuming is verify-ca or ver...

Matt Silverlock•10/16/23, 2:06 PM

No, per the docs: Hyperdrive does not support those modes. We only support

require

require

(and prefer, but we ultimately require TLS).

Colin•10/16/23, 2:06 PM

and the “newer” AWS CA requires the client (Hyperdrive) to have it in its trust store.

I'm a little unsure what you meant by this bit then

Colin•10/16/23, 2:06 PM

If we're only using

require

require

wouldn't cert validation not take place?

CColin If we're only using `require` wouldn't cert validation not take place?

Matt Silverlock•10/16/23, 2:07 PM

Let's step back a second.

You are using Hyperdrive and having issues when using the
```
rds-ca-rsa2048-g1
```
```
rds-ca-rsa2048-g1
```
CA, correct?
When using the raw TCP
```
connect()
```
```
connect()
```
API without Hyperdrive you have no issues, correct?

Colin•10/16/23, 2:08 PM

correct

CColin correct

Matt Silverlock•10/16/23, 2:10 PM

They both share the same egress/TLS path, so this is odd. We shouldn't be validating the cert.

Matt Silverlock•10/16/23, 2:10 PM

(We'll look into it)

Colin•10/16/23, 2:11 PM

I should add there’s a little bit of fuzziness - I couldn’t immediately see results when changing the database CA, it took <=10m

CColin I should add there’s a little bit of fuzziness - I couldn’t _immediately_ see re...

Matt Silverlock•10/16/23, 2:11 PM

AWS says that changing the CA is not an immediate action

Colin•10/16/23, 2:12 PM

I interpreted that in the context of it waiting for the next maintenance window (which we forced immediately), not that there’d be propagation delay

const client = new Client({ connectionString: context.env.DB_HYPERDRIVE.connectionString, }); // Connect to our database console.log("START CONNECT"); await client.connect(); console.log("END CONNECT"); // Test query console.log("START QUERY"); const result = await client.query({ text: "SELECT * FROM pg_tables", }); console.log("END QUERY"); // Returns result rows as JSON return context.json({ result: result });

I keep getting " not_entitled [code: 10000]" even though I can connect to the db via datagrip just f

Similar Threads

Similar Threads

Similar Threads