Git Product home page Git Product logo

Comments (4)

cdrx avatar cdrx commented on July 4, 2024

#42 is just about recovering from a BrokenProcessPool. It does nothing to prevent the exception in the first place. The exception is raised when the Python process hosting the job exits unexpectedly.

The most likely cause your job is hitting a memory limit and the process is killed.

from faktory_worker_python.

JoaoPedroAssis avatar JoaoPedroAssis commented on July 4, 2024

#42 is just about recovering from a BrokenProcessPool. It does nothing to prevent the exception in the first place. The exception is raised when the Python process hosting the job exits unexpectedly.

The most likely cause your job is hitting a memory limit and the process is killed.

I see. The worker is set with a concurrency of 1, so that means that all the memory available for the k8s pod is also available to that single process (currently 600Mi). But if that limit is exceeded, the pod should be restarted instead of throwing this error. Is there some other memory configurations regarding the worker that I should pay attention? Increasing the number of processes can help with this? (I can always spawn more pods to compensate for the single process in the worker, but more processes per pod seems interesting)

Thanks for the reply! @cdrx

from faktory_worker_python.

cdrx avatar cdrx commented on July 4, 2024

that means that all the memory available for the k8s pod is also available to that single process (currently 600Mi).

There are two processes. The master process, which starts a second process - the child (worker) that actually runs your job. Linux will kill the child process if is using more memory than the k8s allows. K8s will only restart the pod if the master process dies.

If you have a concurrency of 1, you can try to use threads in the worker instead. This is done by passing use_threads=True at Worker creation.

It will run only a single process, so k8s will notice if it is killed for ignoring a memory limit.

from faktory_worker_python.

JoaoPedroAssis avatar JoaoPedroAssis commented on July 4, 2024

Thanks! I tried this today and the error has not appeared, but I'll have to wait until some real users try the service and see if the error appears again. In the meantime, do you kwnow some form of measuring each process memory consumption? it will help in the future so I dont need 1 pod per worker and can up the concurrency a bit

from faktory_worker_python.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.