09:16:41 GMT What is the redis server Performance when the dump.rdb file have no write permission? 09:27:56 GMT Athavan: that question makes not much sense 09:30:10 GMT @badboy My Redis error log says "Could not open dump.rdb . Permisssion denied" . Is there any possibility that my redis server slows down because of this error? 09:31:09 GMT no 09:31:14 GMT What are the sideeffects when this Write permisssion is forbidden to dump.rdb file ? 09:35:14 GMT Athavan, I believe that causes redis data to not persist between restarts? 09:35:32 GMT besides that it should operate normally, with no speed slowdowns 09:35:56 GMT IIRC data is only saved to dump.rdb, not ever read except for at database startup 09:43:47 GMT How Can I kill all the clients connected when max Client is reached in redis? 09:52:46 GMT https://redis.io/commands/client-kill 12:14:01 GMT Can I report bugs without signing up to any online shit? 12:14:43 GMT And speaking of bugs, you might want to update your /topic 12:14:52 GMT Unless 3.2.1 really is the latest version? 12:23:52 GMT as far as I can tell from the website, the only way to report a bug is via the google group 12:28:29 GMT ChoHag: what's the bug? 12:32:30 GMT hello guys, what is the best data type in redis to control a job queue system? i need to receive data, put on redis as queue and another worker will find this queue jobs process and remove it. 12:33:14 GMT Oh no. I'm getting seriously pissed off with these me-too CADT projects and their retarded restrictions on bug reports. If redis doesn't want me reporting bugs then I won't. 12:33:19 GMT It's in good company after all. 12:33:23 GMT I will need control the queue job limit and find if data is already in queue. 12:33:59 GMT See I can set up stupid hoops to jump through, too. 12:37:22 GMT sheikpunk, maybe two lists with using RBOPLPUSH, something like what is described here? https://danielkokott.wordpress.com/2015/02/14/redis-reliable-queue-pattern/ 12:38:33 GMT ChoHag, I'm sure someone in here would be willing to go through the bug and report it if you'd describe it, but I'm curious: what large open source projects have you found which *don't* require signing up to something to submit bugs? doesn't most everything either require a github account, an account to their dedicated bug tracker, etc.? 12:39:58 GMT Perl, debian, openbsd. 12:40:01 GMT Off the top of my head. 12:40:37 GMT ah, cool 12:40:54 GMT It's only the cool kids who insist on that crap. 12:42:07 GMT I don't particularly care if someone in here could fix it. I don't jump through these hoops. You get an email, or at a pinch a web form, or you get to remain buggy. 12:42:20 GMT ChoHag: I think you can report it here 12:42:55 GMT I guess I haven't had to report bugs for any software which doesn't require an account on something, but that probably speaks to the current culture and my lack of experience than anything else 12:43:48 GMT ChoHag: I get that you hate the current setup. Would setting up an email address for bug reports solve the problem you see right now? 12:44:10 GMT Yes. 12:44:48 GMT Cool. In the meantime, do you prefer to state the bug here or you would rather for an email address to be set up? 12:45:41 GMT I will wait. Maybe I'll still be interested when it's available. 12:57:06 GMT Dabo: Thanks. I will read it. 13:09:38 GMT ChoHag: I just sent you a private message 13:11:46 GMT Yes it says ping. 13:11:57 GMT Sort of boring. 18:56:55 GMT so i am using pubsub (redis v3.0.7) for communication between two node.js applications. Right now the pubsub output buffer limit is set at 32mb 8mb 60 (defaults). I publish a string that is ~22MB, it gets consumed, cleared from redis memory (up to ~24 MB back down to ~1.3 MB), and all is well.... 5 minutes later I publish a 7MB string and the connections is 18:56:55 GMT severed. Right now i have verbose logging on. 18:56:59 GMT https://gist.github.com/bberry6/2128ae488da8ec271eef0a38ae3fa128 19:00:45 GMT i shouldve done this before hand... but now ill check to see if changing the buffer limit makes the problem go away. 19:08:50 GMT yep it does make the problem not happen. 19:08:58 GMT (i set it to 0 0 0) 19:09:35 GMT So the question is, if i am sending these strings well outside of the 60 seconds where the first is being consumed and cleared from memory, why is the connection being severed when i send the 2nd string? 22:43:24 GMT If there is a dump.rdb file in the configured 'dir', will redis read that on startup regardless of configuration? we don't define a dbfilename directive in our configuration, and assumed that it would not load the file. This does not appear to be the case - anyone know for sure?