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.

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

EctoJob just suddenly stop. #75

Open
blisscs opened this issue Sep 3, 2020 · 2 comments
Open

EctoJob just suddenly stop. #75

blisscs opened this issue Sep 3, 2020 · 2 comments

Comments

@blisscs
Copy link

blisscs commented Sep 3, 2020

Hi,

We are experiencing that Ecto Job just stops working.

Our setup ->

  • We have no. of elixir nodes (usually 3) set up to connect to one PostgreSQL database.

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.

@mbuhot
Copy link
Owner

mbuhot commented Sep 3, 2020

@blisscs this is the first report I’ve had if ecto_job “just stop working”.

Do you have any log output?

@blisscs
Copy link
Author

blisscs commented Sep 11, 2020

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants