too_many_channels error: "{:error, :too_many_channels}"
#843
Comments
|
Hi All: would it be possible to get a simple |
|
I attempted a solution (v unfamiliar with elixir) ^ |
|
this is an issue with CLI environment correct? |
|
I get this in our production (self-hosted) environment as well, although theoretically this would exist with the Supabase-hosted too (just given that the default is at 100 with no way of overriding it, aside from the linked PR I submitted). |
|
when you use it in self-hosted, do you use the seeded user? would increasing there be enough? |
|
@filipecabaco I was trying to brainstorm a solution (like #866) that would work for both local and self-hosted if that makes sense; I think a CLI solution does definitely fix my localhost CLI issues, it just would leave the self-hosted. |
Bug report
Describe the bug
I'm occasionally getting a
"{:error, :too_many_channels}"on self-hosted/local. Is there a way to increase the number of channels (env var, etc.)? I sawMAX_CONNECTIONSbut that doesn't seem right (channels v. connections).Edit 1
It looks like there is
max_channels_per_client, but I'm not sure/don't see the ability to set this dynamically. I'm not familiar enough with the realtime component to know if this loads dynamically or is set in the db. (It looks like a db row?)Edit 2
Okay so the true dev/local using the CLI does not use the same as self-hosted/docker
supabase/realtime... I checked a deployment, and I see below. Is there a way to override the default of100?The text was updated successfully, but these errors were encountered: