-
Notifications
You must be signed in to change notification settings - Fork 998
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
SQL registry disconnections #3611
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@jeremyary looks like this was fixed and accidentally left open. |
@jeremyary @tokoko We encountered the same issue with Feast version 0.35.0. It seems the issue was resolved for using PostgreSQL as the online store, but when utilizing PostgreSQL as a registry, we cannot configure a connection pool. Instead, we've adjusted the Keepalive idle parameters to a larger value or used a proxy like |
@blopezpi you're right, sorry about that. Have you tried the solution that's suggested in the issue? You can pass
|
Expected Behavior
SQL registry works.
Current Behavior
When a SQL registry is used, there is a chance that we may hit a
psycopg2.OperationalError: SSL connection has been closed unexpectedly
issue. This can happen due to the connection being closed for being idle for too long.Steps to reproduce
Use a SQL registry and set a connection idle timeout at the DB. Create a feature store object to connect to this registry, and wait for the timeout (i.e. don't query the feature store). Then try to query the feature store.
Specifications
Possible Solution
When creating the SQL registry, use
self.engine = create_engine(..., pool_pre_ping=True)
. See https://docs.sqlalchemy.org/en/14/core/pooling.html#pool-disconnectsThe text was updated successfully, but these errors were encountered: