Closed GoogleCodeExporter closed 9 years ago
I'm strongly considering using Redis as a primary IPC messaging platform using
BLPOP. The performance gains
from sockets combined with the ability to control access with file permissions
would be wonderful.
Keep up the excellent work!
Original comment by will.con...@gmail.com
on 15 May 2010 at 5:27
i agree, this feature is a must in some scenarios
Original comment by jan.name...@gmail.com
on 16 May 2010 at 1:52
nice !! i m waiting for it !!
Original comment by saheb...@gmail.com
on 17 May 2010 at 11:15
There is a fork of redis with unix sockets on github:
http://github.com/masroore/redis-unix-socket
Merging would be great.
Original comment by kmeren...@gmail.com
on 17 May 2010 at 11:28
I use Redis extensively in a very performance-critical application. I would
love to see Unix sockets available as well!
Original comment by elreydet...@gmail.com
on 31 Jul 2010 at 6:03
This should be marked as an enhancement, not a defect, but it definitely gets
my vote.
Original comment by wils...@gmail.com
on 31 Jul 2010 at 9:57
I concur, this plus single master many slave would make my applications have a
much higher throughput.
Original comment by WayneESe...@gmail.com
on 1 Aug 2010 at 12:01
@WayneESeguin How many slaves do you want? I may have missed it, but I don't
believe there is a set limit to the number of slaves a master can have.
Original comment by josiah.c...@gmail.com
on 1 Aug 2010 at 5:11
Josiah,
Sorry if I was unclear. Currently there is no limit on slaves that I am aware
of.
The reason I would *love* to have the UDS feature is so that I may run a master
Redis server with one slave on each of my application servers so that each
application can access the Redis data store without the unnecessary overhead of
full network packets and transmission on each server between application and
Redis slave.
~Wayne
Original comment by WayneESe...@gmail.com
on 1 Aug 2010 at 7:53
Wayne: Man, that's a pretty good idea. Now I want to do that too.
Original comment by wils...@gmail.com
on 1 Aug 2010 at 8:53
I would love to have this feature. Salvatore said in his San Fran talk that
this was not a big change (the APIs for UnixDomainSockets are almost identical
to those of TCP sockets) so it will be implemented. It is just a question of
when, which is usually determined by how many people in the community need it.
So this is me voting, yes I would LOVE to have this feature.
Original comment by jaksprats
on 1 Aug 2010 at 11:37
Wilson,
I am very glad you think so, I rather like it myself!
~Wayne
Original comment by WayneESe...@gmail.com
on 2 Aug 2010 at 1:31
I've added Unix domain sockets support to Redis:
* http://github.com/tav/redis/compare/upstream...master
The new config settings are described in this mailing list post:
* http://groups.google.com/group/redis-db/browse_thread/thread/f2e9c0f55ceec5e8
Let me know if it proves useful.
-- Cheers, tav
Original comment by tav%espi...@gtempaccount.com
on 4 Aug 2010 at 3:43
Pieter (as in Salvatore and Pieter) implemented this on his fork, and tweeted
about it a few days ago:
http://github.com/pietern/redis/commits/unixsocket
http://twitter.com/pnoordhuis/status/20087370775
It appears that unix domain sockets will be in the mainline fairly soon.
Original comment by gohan...@gmail.com
on 4 Aug 2010 at 3:54
Excellent news!!! I look forward to this being in 2.0?
Original comment by WayneESe...@gmail.com
on 6 Aug 2010 at 6:33
This has been merged to master. Support for redis-cli and redis-benchmark is
available via the "-s" flag.
Original comment by pcnoordh...@gmail.com
on 4 Nov 2010 at 8:47
...and closing.
Original comment by pcnoordh...@gmail.com
on 4 Nov 2010 at 8:48
Original issue reported on code.google.com by
cd...@bk.ru
on 28 Apr 2010 at 1:49