05:31:07 GMT <guest72> hi All
05:31:44 GMT <guest72> my non volatile keys are getting deleted in noeviction policy set
05:32:09 GMT <guest72> Even not seen any low memeory error
09:55:19 GMT <ll`> hi guys, I am reading a redis tutorial, and when I come up with the hash part, I see this example
09:55:46 GMT <ll`> hmset user:1000 usrname antirez birthyear 2001 verified 1
09:55:56 GMT <ll`> what is the 1000 in user:1000 mean ?
09:56:05 GMT <minus> user:1000 is the key
09:56:07 GMT <ll`> why just use user ?
09:56:08 GMT <minus> no special meaning
09:56:20 GMT <minus> because there may be other users
09:57:29 GMT <ll`> so the datas are look like user:1000 -> {username : antirez, birthyear : 2000, verified : 1} ?
09:57:36 GMT <minus> yes
09:57:58 GMT <ll`> minus: thanks, seem weird for me
09:59:12 GMT <ll`> s/for/to/
09:59:44 GMT <minus> because the user id is mangled into the key name?
10:00:00 GMT <minus> redis doesn't support nested data structures, so that's the only way
10:01:11 GMT <ll`> so if I have many users, I have to set user:1, user:2 ... ?
10:01:50 GMT <minus> yeah
10:02:29 GMT <minus> if you need a list of users you have to put all their ids in a set separately
10:03:19 GMT <ll`> sadd user_set user:1 user:2 user:3 ?
10:03:53 GMT <minus> yeah, somewhat like that
10:04:20 GMT <minus> if you need a user → id mapping you'll have to keep a separate hashmap too
10:04:21 GMT <ll`> minus: got it, thanks a lot
10:04:31 GMT <minus> username*
10:04:58 GMT <minus> of course you can also iterate on all your data but that'd be suboptimal
10:06:57 GMT <ll`> ok, thanks, maybe I'll be better to get through redis tutorial first
12:44:34 GMT <seanbright> i'm on redis 3.0.7 and whenever i execute a SHUTDOWN via the CLI, the redis server stops and restarts - this is on ubuntu
12:44:44 GMT <seanbright> not seeing anything in the init.d script that would restart it
12:45:24 GMT <seanbright> is there a configuration option that i am missing that is causing this behavior?
12:46:19 GMT <Brijesh1> have you installed it using the installation script ?
12:46:47 GMT <seanbright> no, via chris lea's PPA
12:46:56 GMT <Brijesh1> ok
12:47:22 GMT <seanbright> i assume that is not supported, just wondering if the "restart after shutdown" is a redis feature that i do not see documented
12:49:41 GMT <Brijesh1> you can download the tar from here and http://redis.io/download
12:49:55 GMT <seanbright> got it
12:49:56 GMT <seanbright> thank you
12:50:33 GMT <Brijesh1> and after untar you can do  :  cd utils/  ;  ./install_server.sh
12:51:38 GMT <seanbright> i don't want to install from source
12:51:56 GMT <seanbright> i just want to know if restarting after a 'SHUTDOWN' is a built-in feature of redis
12:52:13 GMT <seanbright> something that can be toggled via configuration or command line flags
12:57:36 GMT <seanbright> looks to be systemd related.
12:57:37 GMT <seanbright> thanks
15:35:28 GMT <raspado> hi all, how do i start redis as a different user? i tried --user=<username>
15:37:26 GMT <minus> redis doesn't have a feature to drop privileges; you need to start it with the user you want to run it as
15:39:31 GMT <raspado> minus: so something like daemon --user=$USER redis-server $CONF_FILE?
15:39:54 GMT <raspado> do people normally run redis as root?
15:39:58 GMT <minus> something like that, yeah
15:40:00 GMT <minus> no
15:40:26 GMT <minus> distros use their init script system to drop privs
15:40:37 GMT <minus> and run under a separate user
15:45:51 GMT <raspado> ok thx minus
16:09:27 GMT <raspado> minus: i daemonized the process but the redis log is stll created as root /var/log/redis_6379.log
16:09:56 GMT <raspado> whats a good way to generate the log as the proper user
16:14:14 GMT <Dave> /win/win 24
16:14:20 GMT <Dave> er, yes.
16:14:31 GMT <minus> raspado: check the logfile setting for redis; if it's "" then it will log to stdout and something else is writing the logs for it
16:16:03 GMT <raspado> i've got it defined as logfile {{ redis_log_path }}/{{ redis_log_file }}
16:16:17 GMT <minus> are you sure redis is running as user?
16:16:43 GMT <minus> that looks like ansible configs :D
16:17:12 GMT <raspado> it is ansible :)
16:19:34 GMT <raspado> the svc_redis user doesnt have access to touch the file in /var/log
16:20:03 GMT <raspado> probably best to put it elsewhere?
16:20:04 GMT <minus> you could let the system handle the logging though
16:20:23 GMT <raspado> oh? just making it "" ?
16:20:39 GMT <minus> then it logs to stdout and your system might pick it up
16:20:42 GMT <minus> systemd?
16:21:28 GMT <raspado> yeah
16:21:38 GMT <raspado> centos7
16:21:47 GMT <minus> yeah, it'll just be captured by journald then
16:22:21 GMT <minus> we log info level via stdout/journald and anything more verbose via graylog in the applications
16:24:16 GMT <raspado> cool thx minus
18:57:31 GMT <mak_> is it possible to setup a redis cluster using redis-trib.rb and containers on the same network (each running in cluster mode) ? im getting "Adding node ip:port  to cluster node ip:port. sorry can't connect..." and redis examples all have redis isntances on localhost within the same container
18:58:14 GMT <mak_> containers on the same network, but each having a single redis instance
19:15:54 GMT <kmak20> is it possible to setup a redis cluster using redis-trib.rb and containers on the same network (each running in cluster mode) ? im getting "Adding node ip:port  to cluster node ip:port. sorry can't connect..." and redis examples all have redis instances on localhost within the same container. containers on the same network, but each having a single redis instance. i can connect to each redis container outside the docker network using
19:17:34 GMT <kmak20> sorry for the confusion. my redis instances are on separate containers and on the same subnet with ports open, but i still get this error
19:17:50 GMT <kmak20> no auth
20:46:04 GMT <demetriusnunes> hey all, trying to use the --pipe command with redis-cli together with -h option, but it doesn't work. anybody know how to do it?
21:21:35 GMT <raspado> hi, is the config get * intrusive? i have redis aws instances that aws does not have redis.conf's for so we need to get all the configs via cli but i dont want to blow up prod:)
22:16:07 GMT <ron> yeah, it's not the right time of day for antirez to be around.
22:17:34 GMT <ron> I'll try checking tomorrow.
23:17:29 GMT <willnx> Hello! I have a question about Redis Cluster, and I can't seem to find an answer via the docs or google. I'm wondering what happens to the master's cache if dies, and (something like systemd) respawns before the failover timeout.
23:18:18 GMT <willnx> Does the master attempt to reload the info a slave has? Or will the master just reload that data from the append-only file?