What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Salut everyone, We have noticed some instability while starting using `--stop-when-empty` option on

U0159BVDTEK
U0159BVDTEK Posts: 12 🧑🏻‍🚀 - Cadet
in Help

Salut everyone,

We have noticed some instability while starting using --stop-when-empty option on console queue:worker:start instead of deprecated configuration for keeping work loop, see demo shop commit https://github.com/spryker-shop/b2b-demo-shop/commit/71377ecb7ff423168ab1e278ad62ffa809ccd2f1

The instability about having Jenkins job running infinitely even though there are no events on RabbitMQ, moreover sometimes store has events but they are not processed as dedicated Jenkins job seems finished right after run, like there are nothing to proceed.

Comments

  • UKEP86J66
    UKEP86J66 Posts: 208 🧑🏻‍🚀 - Cadet

    We have seen this too on our project. I suspect it is something to do with slow queue workers (when you have more than the normal demodata)

  • sprymiker
    sprymiker Cloud Platform Architect Sprykee Posts: 781 🧑🏻‍🚀 - Cadet
    edited July 2020

    Hello Sergii,

    You should not use --stop-when-empty for background jobs.

    QUEUE_WORKER_LOOP was deprecated and replaced with --stop-when-empty and should be used only for CI purposes or manually in local env.

    P.S. Also QUEUE_WORKER_LOOP=true should not be used in background jobs as well.

  • U0159BVDTEK
    U0159BVDTEK Posts: 12 🧑🏻‍🚀 - Cadet

    Thank you for your replay Mike! Ok then should we remove "stop-when-empty" from our Jenkins job configuration without setting "QUEUE_WORKER_LOOP" back to our config?

  • sprymiker
    sprymiker Cloud Platform Architect Sprykee Posts: 781 🧑🏻‍🚀 - Cadet

    Right. At that point q:w:s will be run for 1 minute only.

  • U0159BVDTEK
    U0159BVDTEK Posts: 12 🧑🏻‍🚀 - Cadet

    Ok, thank you for your help.

  • sprymiker
    sprymiker Cloud Platform Architect Sprykee Posts: 781 🧑🏻‍🚀 - Cadet

    You’re welcome!

Categories