15:28:40 GMT <lieter> hi, quick question, is it possible to have redis write to an included file on CONFIG WRITE?
15:30:15 GMT <minus_> didn't know redis supports includes
15:30:57 GMT <minus_> looks like it doesn't
15:32:53 GMT <lieter> meh
15:33:12 GMT <lieter> so there is some bad interaction between using the sentinel and having config management
15:33:43 GMT <lieter> there are several 'unless'es here
15:34:06 GMT <minus_> yeah know what you mean :/
15:34:36 GMT <lieter> but lineinfile might bet me there
15:34:40 GMT <minus_> cluster stores its config in a separate file, that was solved better
15:34:57 GMT <lieter> I don't need cluster I think
15:35:26 GMT <minus_> i'd just go with overriding all config files (redis and sentinels) if i have a change
15:35:30 GMT <lieter> I want 3 nodes to be a (possible) master, sentinel and sa bunch of slaves local to the client
19:51:22 GMT <hipposwagamus_> I'm using Redis for it's pub/sub capabilities and at the beginning of an application I subscribe to a specific channel that should only see specific "keep alive" messages. Whenever I put the Redis cluster under pressure, by creating a lot of subscriptions and sending a lot of messages, the original channel I subscribed to always sees an error like: ERR Protocol error: invalid bulk length, ERR Protocol error: invalid multibulk l
19:51:50 GMT <hipposwagamus_> Does anyone have ideas as to why this could be happening?
20:35:28 GMT <elad_> *sigh* hello
20:37:11 GMT <elad_> quick question. suppose I want to limit redis's memory usage, but have the OS take care of swapping. is this possible? or will redis actively try to be "smart" and refuse to store data that exceeds available memory?
21:00:05 GMT <minus_> you can set the memory limit for redis, otherwise it'll consume memory until it gets killed. it'll get swapped like other programs. at least that's what i assume, can't really guarantee what i said is correct
21:04:44 GMT <elad_> minus_: the configuration seems to imply that if I use a "no eviction" memory policy redis will start erroring once it hits the memory limit.
21:05:43 GMT <minus_> yes, but that assumes you have a memory limit set
21:06:00 GMT <elad_> so you're saying I should set an rlimit instead and let redis assume it has all available memory?
21:06:09 GMT <minus_> i guess it will also error if it can't alloc memory from the OS, but at that point something's pretty sure to crash
21:06:39 GMT <minus_> no, use redis' max-memory config option
21:20:21 GMT <hipposwagamus_> This isn't necessarily a Redis question but I'm using Jedis and I cannot figure out if the JedisPubSub class is meant to be used as a singleton, or should I create a new JedisPubSub object for every new subscription. Does anyone know the proper usage?