Skip to content
This repository was archived by the owner on Aug 28, 2019. It is now read-only.

add the queue name processed by the worker in the 'queue' key#16

Merged
gregberge merged 1 commit intogregberge:masterfrom
desbouis:queue-name-in-worker-info
Jul 22, 2014
Merged

add the queue name processed by the worker in the 'queue' key#16
gregberge merged 1 commit intogregberge:masterfrom
desbouis:queue-name-in-worker-info

Conversation

@desbouis
Copy link
Copy Markdown
Collaborator

It's usefull to know the queue processed by a worker with a simple redis command like hgetall.
So I store the queue name in the 'queue' key in the redis hash of the worker.

@gregberge gregberge added the feat label Jul 22, 2014
@gregberge gregberge self-assigned this Jul 22, 2014
gregberge added a commit that referenced this pull request Jul 22, 2014
add the queue name processed by the worker in the 'queue' key
@gregberge gregberge merged commit 5502e2b into gregberge:master Jul 22, 2014
@Yvem
Copy link
Copy Markdown

Yvem commented Aug 8, 2014

I don't understand. workers have a redis entry ? Aren't they redis clients only ?

I may not understand well, but if yes, internal design would be a nice addition to node-taskman readme.

@gregberge
Copy link
Copy Markdown
Owner

Yes workers have status in redis, the goal is to be able to control them without reloading the program. The original design was done by @desbouis, you can ask him about the philosophy!

@Yvem
Copy link
Copy Markdown

Yvem commented Aug 8, 2014

Nice. That's an interesting feature that should be documented.

@desbouis desbouis deleted the queue-name-in-worker-info branch October 3, 2014 16:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants