-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Websocket connection stops working after few days #2953
Comments
Hi @gyan - thanks for reporting. Graph Node's current subscriptions implementation is known not to be resilient, which may be what you are seeing here. We have a refactor planned, but have not got to it yet. What are you using the websocket connection for? |
Thanks for the update @azf20 Our graph server is supposed to index high frequency data and deliver the same to the subscribed client. So, subscriptions seemed a great way to cater to this problem. |
OK - yes interval based polling is the most reliable & recommended approach at this point, though we will hope to enable better support your high frequency requirement with subscriptions in future |
Hi @azf20 |
Hi @azf20, |
hey @nakamuraos and @gyan - no additional update for now. As mentioned websockets are not currently recommended due to instability |
@azf20 Hi! Wondering if there are any updates regarding websocket support, including on the hosted service. It would make our frontend a lot simpler/responsive if we could just subscribe to updates. |
Subscriptions are no longer supported |
Bug
I am running graph-node in a dockerized environment inside aws ec2. Both https and wss endpoints work fine, but after few days the websocket endpoint suddenly stops responding and request finishes after almost 5-10 seconds.
When I restart the container, everything works normally as expected and the issue repeats itself again after sometimes.
The text was updated successfully, but these errors were encountered: