search

chaps-io / gush

Fast and distributed workflow runner using ActiveJob and Redis
MIT License
1.03k stars 103 forks source link

Gush.configure with namespace issue #62

Closed Ranjithkumar closed 5 years ago

Ranjithkumar commented 5 years ago

In the Gush.configure, If we add namespace XXX then sidekiq is not pulling the jobs.

If we add namespace as "gush" then its pulling the job.

pokonski commented 5 years ago

You have to explicitly tell sidekiq which queues to use, so if you specify xxx as namespace/job queue you have to run sidekiq with that queue as argument:

bundle exec sidekiq -q xxx -q some_other_queue

Basically you have to list all the queues you intend to use so sidekiq knows.

Ranjithkumar commented 5 years ago

@pokonski I guess there are some confusion. Please check my attachment gush 2018 11 23 12 32 38

Gush::Client takes default namespace as 'gush'. For Jobs, I am using queue name as 'rans'. I am running sidekiq using sidekiq -C config/sidekiq.yml It has all the queue information. Its working fine with this config.

If I change the Gush::Client namespace to 'gush_dev' then its not processing the jobs.

Ranjithkumar commented 5 years ago

@pokonski Its working fine with version 2.0.0!