You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 6, 2024. It is now read-only.
I just wanted to share with you an issue regarding the event stream. If we have a large amount of data from the Event Update Log it tends to hit an API in one go and can cause timeout. The most common timeout is from RQJob timeout and when I check the pull_from_node function, it uses the default queue which takes 300 seconds.
Is it possible if we can use custom worker for event stream, or maybe we can extend the timeout and batched the process of notify the consumer site?
Hi,
I just wanted to share with you an issue regarding the event stream. If we have a large amount of data from the Event Update Log it tends to hit an API in one go and can cause timeout. The most common timeout is from RQJob timeout and when I check the pull_from_node function, it uses the default queue which takes 300 seconds.
Is it possible if we can use custom worker for event stream, or maybe we can extend the timeout and batched the process of notify the consumer site?
Thank you in advance