01:34:52 GMT Hello guys. I just set up a Clustered Redis on AWS with 1 shard and 1 replica, giving me 2 nodes. When I do a GET (key) on the second node, I get a MOVED response for all keys. Are they not supposed to serve the same data when they are the same shard? 01:37:53 GMT Nobody? 01:38:16 GMT CLUSTER INFO is identical, yet only one node "works" 01:50:03 GMT I found out. I just needed to do READONLY. Then it worked. 01:50:11 GMT good talk 05:30:56 GMT hello, can anyone tell me how to get num-other-sentinels to report the correct number? We ran into some issues today and had to reset the sentinels and move the service from 1 node to a new node and now num-other-sentinels reports 3 instead of 2 as it should. 17:07:03 GMT We have a server that has a key space of about 0.5mb but we are consuming 28gb of ram with an AOF file around 24gb. We aren't sure how or why it is consuming that much space so any tips would be appreciated 17:15:58 GMT melkore: please paste the output of the "INFO" command 17:16:08 GMT (but please do not paste it here, put it in a gist or similar) 17:20:43 GMT https://paste.fedoraproject.org/510145/ 17:22:11 GMT how did you determine that your key space needs about 0.5mb? 17:23:52 GMT ran redis-cli --bigkeys 17:24:04 GMT all until the end? 17:25:24 GMT there's less than 8100 keys in there with and avg size of 1.05 17:29:26 GMT that is weird 17:30:11 GMT That's what I was thinking. This shouldn't be chewing on much at all for resources 17:30:24 GMT you could try to load the aof in a new instance and see if that fixes it^^ 17:36:37 GMT hmm I'll have to see if we can arrange that to test. So nothing is really standing out? I was initially assuming it was just growing because there was more memory on the machine but that doesn't make much sense 18:14:01 GMT melkore: not using multiple databases are you? 18:48:04 GMT single node 18:58:07 GMT oh right 18:58:14 GMT you _do_ have 7 keys in db 7 18:58:14 GMT db7:keys=7,expires=0,avg_ttl=0 18:58:24 GMT in theory they could old gigabytes of data^^ 19:00:17 GMT I'll take a look, the server isn't heavily fragmented with mem_fragmentation_ration at 1.0 so that's good 19:00:58 GMT yep 19:01:04 GMT it's not fragmented at all ;) 19:01:49 GMT It has enough room at the moment but we had to double the ram recently to get it to behave again. Trying to figure out /why/ it suddenly jumped up has been a challenge