edgedb: ERROR InternalServerError: [Errno 24] Too many open files

ERROR InternalServerError: [Errno 24] Too many open files
Hint: This is most likely a bug in EdgeDB. Please consider opening an issue ticket at https://github.com/edgedb/edgedb/issues/new?template=bug_report.md

    at RawConnection._parseErrorMessage (https://deno.land/x/edgedb@v1.4.1/_src/baseConn.ts:305:17)
    at RawConnection._executeFlow (https://deno.land/x/edgedb@v1.4.1/_src/baseConn.ts:1139:24)
    at eventLoopTick (ext:core/01_core.js:182:7)
    at async RawConnection.fetch (https://deno.land/x/edgedb@v1.4.1/_src/baseConn.ts:1250:9)
    at async ClientConnectionHolder.retryingFetch (https://deno.land/x/edgedb@v1.4.1/_src/baseClient.ts:177:18)
    at async Client.querySingle (https://deno.land/x/edgedb@v1.4.1/_src/baseClient.ts:615:14)
    at async findDomain (file:///Users/netopwibby/Projects/Beachfront/api/src/component/search/crud/read.ts:507:36)
    at async file:///Users/netopwibby/Projects/Beachfront/api/src/component/search/crud/read.ts:436:26
    at async Promise.all (index 56)
    at async createCollection (file:///Users/netopwibby/Projects/Beachfront/api/src/component/search/crud/read.ts:425:3)

EdgeDB Version: 3.0+7d903be
EdgeDB CLI Version: 4.0.2+500be79
OS Version: macOS Sonama (14.2.1)

I’m building a domain registrar and the API queries EdgeDB before using external APIs to populate search results. The results vary in length (from as little as 2 to as many as 100+). The database is queried a LOT for each search so maybe that’s the issue?

I came across this issue while returning to a background tab so it’s possible something was hanging while I was away. Not sure if this issue is a query error but I can share my schema if it’ll help.

About this issue

Original URL
State: open
Created 6 months ago
Comments: 15 (6 by maintainers)

Most upvoted comments

Yes, one client is the recommended workflow

msullivan on Feb 15, 2024

Yeah, you should just have one client, probably. You’ll be establishing way more connections than you need to otherwise. The client does connection pooling internally too, I think, so you might be making even more connections than you realize.

That said we should be producing a clean error message instead of an InternalServerError.

You don’t need to (and, it seems, must not) specify the database name when running edgedb instance logs. It’s all one instance, they share logs.

msullivan on Feb 15, 2024