07:19:52 GMT <minus> harej: redis doesn't do any magic on key names afaik; and yes, using hashes uses less memory
07:20:12 GMT <harej> Thank you minus
08:39:09 GMT <wasanzy> hello
08:39:45 GMT <wasanzy> in my redis sentinel log, I found this errors: # +sdown master
08:39:54 GMT <wasanzy> # +odown master
08:40:16 GMT <wasanzy> failover-abort-not-elected master
08:40:42 GMT <wasanzy> whenever this message appears in the logs, I get error from application "Could not get resource from pool"
08:40:45 GMT <wasanzy> any idea?
08:49:03 GMT <minus> your master is down and failover failed
08:49:42 GMT <wasanzy> yes so what could cause the master to go down? there was no restart or anything
08:49:51 GMT <wasanzy> redis logs does not give me any reason too
09:01:23 GMT <minus> no idea what could cause the master to go down, but odown and failover failing means that the majority of sentinels judged the master to be done but didn't reach the required quorum to actually perform the failover
09:07:32 GMT <wasanzy> and it looks like it is not able to make use of the slave.
09:07:51 GMT <wasanzy> # +vote-for-leader 31a3dfbe4e96f93eb0b02193f79ce3bb14e1be7c 2678891
09:16:12 GMT <minus> you have 2 redises and 3 sentinels?
09:19:12 GMT <fbred> is it a bad idea to have ~40 sentinels?
09:20:06 GMT <fbred> I decided to have sentinels on all webservers, so they can connect to localhost and ask who is the master, but I'm seeing high traffic on idle redis instances, which i thought might be to the volume of sentinels communicating
09:22:37 GMT <wasanzy> minus: i hv two redis and two sentinel
09:23:33 GMT <wasanzy> so the sentinels are on the same servers as redis. 2 servers
09:26:12 GMT <minus> i don't think that two sentinels work
09:26:31 GMT <minus> it's strongly recommended (if not required) to run an uneven number, at least 3
09:26:43 GMT <efphe> me too I have 3 sentinels
09:26:54 GMT <efphe> two on the redis servers and another one elsewhere to keep evenness
09:27:12 GMT <wasanzy> I need 3 sentinel?
09:27:20 GMT <efphe> wasanzy, imho yes
09:27:23 GMT <efphe> it's better
09:27:47 GMT <wasanzy> so which one will be responsible for selecting the master?
09:27:51 GMT <efphe> (not a redis hackers but the docs are pretty clear here as minus says)
09:28:55 GMT <badboy_> yes, pick 3 Sentinels. You need N/2+1 Sentinels to agree on the failover. With 3 you can sustain one unavailable Sentinel, with 2 you can't
09:29:43 GMT <wasanzy> right so I use Haproxy as the proxy balancer so haproxy connects to sentinel and sentinel tells which redis is currently the master
10:31:44 GMT <minus> you can also have haproxy ask both redis servers if they're master and only take the master one online, but that's unrelated to the sentinel problem
10:36:25 GMT <wasanzy> minus: meaning there is no need for sentinel?
10:36:59 GMT <badboy_> if you want automatic failover you still need it
10:39:15 GMT <wasanzy> ok
10:39:22 GMT <wasanzy> how do I check redis version?
10:40:27 GMT <wasanzy> redis-cli -v
10:40:28 GMT <wasanzy> seen
10:46:33 GMT <wasanzy> do I need redis on the third server or just sentinel?
11:29:40 GMT <minus> wasanzy: just sentinel
11:29:43 GMT <minus> read the tutorial
11:37:23 GMT <wasanzy> ok
11:46:04 GMT <wasanzy> this doc doesn't show how to install sentinel
11:46:08 GMT <wasanzy> https://redis.io/topics/sentinel
12:49:40 GMT <JeremyS> hello! I am researching redis as a k/v store and in trying to plan out how it might be utilized in our case I had a few questions I hope someone can help with.
12:51:08 GMT <JeremyS> is there any way(outside of connecting to an entirely separate redis server), to limit what keys will be synchronized to a slave redis?