Hey guys , I am setting up cluster node is getting added successfully but cluster-node info is fail
how can i debugg information
Hi, guys... I am starting with redis and have one quick question... I have a system with app and workers. I want to run rpush from app and send message that I did push. Then, I want to rpop from workers and the one who rpops first gets that task. Do you think that is a good idea?
This gives me ability to later in worker if there are too many tasks it got to ignore new tasks and introduce worker for scaling which will detect when there are no enought workers.
Do you see anything wrong with it?
that's how it's usually done
just blpop on the worker side
saves you the "send message" part
I kind of wanted to be able to deny certain tasks on certain workers, that is why it made sense to me
Well, I will do it later... For now, as recommended... Thank you! :D
As I understand it Sentinel can monitor multiple Redises, can it also control the slave priority? I'm running multiple, independent Sentinel managed Redis groups across a pool of nodes, and with the default fixed priority they all want to bunch up on node 1.
I'm looking into managing slave-priority to resolve this, but I've come to the conclusion whatever manages that setting needs to know the state of all the redises to properly pick which node is the best failover slave. As such I'm wondering if this feature would be best done by Sentinel, as Sentinel tracks that information already.
What will happen if my worker send BRPOP and crash/disconnect?
And there is nothing in queue
Will someone else get that result or will it be lost?
Related: Is there any way to set the run-id to a preset value? I think this would be better than slave-priority for node favoring as the it wouldn't override replication offset, and I could use this to resolve a Sentinel issue I'm having in containers. I'm not finding much on how the run-id is generated in the docs, but I may be overlooking it.
greps the source
Hrm, per the comments on getRandomHexChars() pinning run_id probably isn't the best of ideas, even if it was supported which it isn't.
On second thought I think it's best to leave slave-priority alone, I don't like that it overrides the replication offset. It would be nice if there was a way to set a priority value that's weighted less than replication offset, but per the sentinel docs there isn't one.
I want to push a list of strings into redis, and pop it out one at a time so that multiple processes can independenty do work
should i use a queue?