We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
We are experiencing that Ecto Job just stops working.
Our setup ->
We continue to experience that Ecto Job just stop working. And we have to restart our elixir node to make things start working again.
When Ecto Job stops working, we can observe that there are unprocessed records (around 15-30 records) in AVAILABLE states in the job_queue table.
AVAILABLE
Please recommend how to check this issue and to protect this from happening again.
The text was updated successfully, but these errors were encountered:
@blisscs this is the first report I’ve had if ecto_job “just stop working”.
Do you have any log output?
Sorry, something went wrong.
@mbuhot ,
Sorry for the delay, I have no log of the issue.
What I could observe is that I have many network heavy tasks in the queue. And these network calls are usually timed longer than ecto multi's timeout.
I think with so many tasks like this, it eventually cause some effects to stop.
No branches or pull requests
Hi,
We are experiencing that Ecto Job just stops working.
Our setup ->
We continue to experience that Ecto Job just stop working. And we have to restart our elixir node to make things start working again.
When Ecto Job stops working, we can observe that there are unprocessed records (around 15-30 records) in
AVAILABLE
states in the job_queue table.Please recommend how to check this issue and to protect this from happening again.
The text was updated successfully, but these errors were encountered: