09:39:53 GMT <cloudbud> can someone send me the init script for redis 3.2  for ubuntu
09:41:34 GMT <colo-work> you can download the deb and extract it yourself
09:41:36 GMT <colo-work> http://mirrors.kernel.org/ubuntu/pool/universe/r/redis/redis-server_3.2.1-1_amd64.deb
09:41:43 GMT <colo-work> ar x redis-server_3.2.1-1_amd64.deb
09:41:49 GMT <colo-work> tar xf data.tar*
09:43:59 GMT <cloudbud> colo-work : do we have deb file for 4.0 redis also ?
09:44:49 GMT <Bish> when having a integer as string, there will be no way to increment inside a multi thingie, right?
09:54:01 GMT <colo-work> cloudbud, Debian has one (in sid/experimental); don't know about Ubuntu
09:57:49 GMT <cloudbud> colo-work : do you have any link where I can install redis from source and then make it run as deamon
09:57:58 GMT <cloudbud> i have installed it using source
09:58:07 GMT <cloudbud> but dont know how to run it is deamon
09:58:14 GMT <colo-work> cloudbud, what kind of init system does your host-OS use? systemd?
09:58:24 GMT <colo-work> if so, just write (or use) a service unit file for it
09:58:33 GMT <cloudbud> its ubuntu 14
09:58:43 GMT <colo-work> ah, so upstart then :/
09:59:04 GMT <colo-work> you might want to fet the redis source package for the version included in ubuntu 14 then
09:59:14 GMT <colo-work> and just adapt its upstart script for your new service
09:59:48 GMT <colo-work> (in essence, it's just substituting the new path to redis-server from your from-source build for the distro-provided one)
10:00:10 GMT <colo-work> I don't know upstart, so I'm afraid I can't provide any more/better hints
10:00:14 GMT <colo-work> on how to do that correctly
10:00:18 GMT <colo-work> #ubuntu might know
10:00:49 GMT <minus> urgh upstart
10:02:15 GMT <cloudbud> any blog or any reference
10:20:37 GMT <cloudbud> is there any tutorial to fine tune redis server
11:37:21 GMT <cloudbud> how to resolve this /var/run/redis-server.pid exists, process is already running or crashed
12:38:07 GMT <wasanzy> sentinel seems to be switching master more often but when I check redis, it seems to be running fine. why does sentinel switch more often?
13:08:54 GMT <colo-work> cloudbud, make redis and its init script use another path for its pid file
13:18:23 GMT <wasanzy> sentinel seems to be switching master more often but when I check redis, it seems to be running fine. why does sentinel switch more often?
13:19:06 GMT <colo-work> wasanzy, the sentinel instances display details about their decision making process in their logs
13:20:51 GMT <wasanzy> colo-work: yes I see that. but the logs doesn't tell much. and also, I see lot of sdown etc and after that a failover is performed. Redis on the other hands is working fie so I don't see why there should be fail overs
13:21:47 GMT <colo-work> well, sdown means just that. _s_ubjectively down. for that sentinel instance, the monitored redis instance is unavailable.
13:23:14 GMT <wasanzy> sample log: https://paste.linux.community/view/c67152a0
13:24:32 GMT <wasanzy> the master and slave redis is always available so sentinel is confusing me a little. How can I reduce the number probability of a switch over?
15:59:23 GMT <gojinjedi> question: am I assuming right: AOF and RDB is on by default when first installing redis?
15:59:43 GMT <gojinjedi> if not which one is on by default...?
16:00:28 GMT <minus> gojinjedi: RDB is on by default
16:01:13 GMT <minus> well, in the example config and when you don't provide a config. as soon as you pass redis a flag or don't have 'save' or so in the config it won't persist
16:01:52 GMT <gojinjedi> ok thanks, good to know
16:02:17 GMT <gojinjedi> wasn't quite clear what was the default in the docs.
17:33:07 GMT <gojinjedi> is this normal? doing "save 60 1000" to set RDB options gives me an error
17:44:19 GMT <harikb> 2:57 PM <harikb> Anyone know if pipeline feature works on a redis-cluster? looking for latest on this https://github.com/nrk/predis/issues/267 and this  https://groups.google.com/forum/#!msg/redis-db/4I0ELYnf3bk/Lrctk0ULm6AJ