Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When HTTP2 connection turns to read_only, it's not recovered #120

Closed
nallwhy opened this issue Feb 16, 2021 · 5 comments
Closed

When HTTP2 connection turns to read_only, it's not recovered #120

nallwhy opened this issue Feb 16, 2021 · 5 comments

Comments

@nallwhy
Copy link

nallwhy commented Feb 16, 2021

When my HTTP2 connection turns to read_only, it keeps return read_only error until I restart my app.

{:error, %{reason: :read_only}}

Setting:

defmodule MyApp.Application do
  use Application

  def start(_type, _args) do
    children = [
      {Finch,
       name: MyApp.FintchPool,
       pools: %{
         :default => [protocol: :http2]
       }}
    ]

    Supervisor.start_link(children, strategy: :one_for_one, name: MyApp.Supervisor)
  end
end
@sneako
Copy link
Owner

sneako commented Feb 17, 2021

Thanks for the report @nallwhy. I can confirm this is an issue and we will have to find some time to look into it

@keathley
Copy link
Collaborator

I can take a look into this. We need to get some pbt around that since there are a bunch of ways to end up in a bad states like this.

@nallwhy
Copy link
Author

nallwhy commented Feb 21, 2021

I guess that closing connection from host makes state of connection to read_only, and reconnection doesn't work.
I use finch to call google API.

@rhpts
Copy link

rhpts commented Sep 30, 2021

BTW, when the HTTP2 connections gets into the {:error, %{reason: :read_only}} state, is it possible to restart the :finch application via the console (iex or remsh)?

@nallwhy
Copy link
Author

nallwhy commented May 24, 2022

I no longer have this problem.

@nallwhy nallwhy closed this as completed May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants