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.

Sign up for GitHub

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

Jump to bottom

Production logs: "Failed to receive notification: conn closed" #2032

Closed
matt2e opened this issue Jul 10, 2024 · 2 comments
Closed

Production logs: "Failed to receive notification: conn closed" #2032

matt2e opened this issue Jul 10, 2024 · 2 comments
Assignees
@wesbillman
Labels
P1

Comments

@matt2e
Copy link
Collaborator

matt2e commented Jul 10, 2024 •
edited

Logs:

  • Happens twice every few seconds
  • Code is in dal.notify.go here where we listen to events streamed from the db
  • First thought is why is the connection closing...?
@github-actions github-actions bot added the triage Issue needs triaging label Jul 10, 2024
@ftl-robot ftl-robot mentioned this issue Jul 10, 2024
Open
@matt2e matt2e added next Work that will be be picked up next P1 and removed triage Issue needs triaging labels Jul 11, 2024
@wesbillman
Copy link
Member

I wonder if there's a difference in the production set up that is causing timeout issues for long running connections.

@wesbillman wesbillman self-assigned this Jul 15, 2024
@github-actions github-actions bot removed the next Work that will be be picked up next label Jul 15, 2024
@wesbillman
Copy link
Member

Migrated the controller off of the pg_notify version in favor of polling. We might want to revisit this in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wesbillman wesbillman

Labels
P1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wesbillman @matt2e