11:03:54 GMT Hello. Why sentinel remove is not considered valid configuration statement? 11:27:17 GMT geeze, I was looking forward nice ansible role, but this. 12:26:08 GMT dosmanak: because it is a command 12:26:22 GMT the configuration file isn't really the place to do dynamic reconfiguration 12:28:03 GMT So why redis stores its dynamic configuration into this file. 12:28:36 GMT Design Decision ^^ 12:29:14 GMT Althought I appended include of my setting at the end of the file, then new lines are appended at the end, so my local config is not true anymore. 12:31:34 GMT yes 12:32:03 GMT Sentinel is not particular friendly to be fully managed by configuration management systems 12:32:31 GMT So I cannot prepare static config file, which will get my redis architecture into known state. 12:33:23 GMT Ok, thanks for discussion, I will try different aproach :-) 12:33:46 GMT You can use an initial config file, but Redis will rewrite it, yes 12:37:39 GMT One more thing. 12:38:14 GMT Oh, not really, bad idea :-) 12:39:03 GMT But it seems feasible to maintaing basic configuration in systemd service. 12:42:30 GMT But still sentinel monitor is command and config statement, but sentinel remove is only command, oh man... 13:36:02 GMT hi 13:37:11 GMT is it necessary to use a redis instance (c = redis.Redis()) in case of multithreaded applications ? (I mean for each threads) 14:14:25 GMT Check your client library's documentation on whether it is thread-safe 14:34:40 GMT long gone, badboy_, long gone. 14:35:09 GMT :D 15:43:31 GMT Migrating redis data always seemed like a daunting task, but I just discovered that I can set one instance as a slave of another, and all the data replicates so quick. I set up an SSH tunnel to a remote server hosting 11GB of redis data, and within about five minutes, it was all replicated on the slave. I set it back to a master and the job was done. I just wanted to share this. Fantastic experience. 15:53:09 GMT if you need to clone all data, yeah 22:55:53 GMT hello everyone, i was curious if anyone has seen an issue where after increasing 'hz', memory exponentially increases. I'm seeing this after i bumped hz from 100 to 500. despite reverting the change, memory is still slowly getting consumed and never releasing.