We have 3 memcached server and we are using individual IP address in
application. is it possible to create Cluster if yes then please share
setup recommendation step by step
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe
Thanks guys, this is quite helpful
In the same vein, can we also say that memcache replication is also a
client side driven solution?
--
---
You received this message because you are subscribed to the Google Groups
memcached group.
To unsubscribe from this group and stop receiving emails
Also, anyone heard about repcached? Is this a patch users would need to
add in order to get data replication feature? Does memcached endorse this?
--
---
You received this message because you are subscribed to the Google Groups
memcached group.
To unsubscribe from this group and stop
On Tue, Mar 4, 2014 at 2:56 AM, Ranjit D'Souza bernard@gmail.com wrote:
Thanks guys, this is quite helpful
In the same vein, can we also say that memcache replication is also a client
side driven solution?
In the stock system, there is no replication - although I believe
others done it
FYI, I have written a memcached compatible KVS named yrmcds that implements
master-slave replication.
As this is slightly off-topic from the list, please ask me directly if you
are interested in it:
http://cybozu.github.io/yrmcds/
@ymmt2005
On Tuesday, March 4, 2014 6:33:24 PM UTC+9, Ranjit
I have a basic question:
Does memcached support clustering and HA out of the box, or does it need
some third party integration in order to do so?
Thanks,
Ranjit
--
---
You received this message because you are subscribed to the Google Groups
memcached group.
To unsubscribe from this group
On Mon, Mar 3, 2014 at 6:01 AM, Ranjit D'Souza bernard@gmail.com wrote:
I have a basic question:
Does memcached support clustering and HA out of the box, or does it need
some third party integration in order to do so?
Yes, but it is a cache, not a persistent store so the way it handles
Thank you
Is there any concept of master-slave configuration (like in Redis), and
promoting the slave to master?
Can you point me to a document or wiki link that gives more information on
how to set up a memcached cluster?
--
---
You received this message because you are subscribed
@gmail.comwrote:
Thank you
Is there any concept of master-slave configuration (like in Redis), and
promoting the slave to master?
Can you point me to a document or wiki link that gives more information on
how to set up a memcached cluster?
--
---
You received this message because you
on
line.
Can you point me to a document or wiki link that gives more information on
how to set up a memcached cluster?
The server side is packaged for some Linux distributions. You just
configure the amount of memory for it to use on each node.
--
Les Mikesell
lesmikes...@gmail.com
Hello Dormando!Thanks for your reply.
Description and requirements are:
- Memcached will be used a primary storage (i.e. not for caching MySQL).
- It should have failover feature (in case if one server fails all
connections goes to another server).
Basically something like Master-Slave
It's really a discussion for another mailing list, but if you could
elaborate to me directly or to couchb...@googlegroups.com, I'd be
interested in why you say Couchbase is much slower. I've not seen it that
way.
Full disclosure, I'm a couchbase person. I also do a lot of work on the
has master-slave capabilities; CraigsList at one point was built on
40 Redis nodes. [1] Also, if I'm not mistaken, Riak [2], MySQL Cluster [3],
and AWS ElastiCache [4] (probably several more: couchdb, cassandra...) all
offer more or less what you'd expect from a memcached cluster.
Redis
Hello Dormando!
Thanks for your reply.
Description and requirements are:
- Memcached will be used a primary storage (i.e. not for caching MySQL).
- It should have failover feature (in case if one server fails all
connections goes to another server).
Basically something like Master-Slave will be
Dear memcached community,
It would be really good to build a failover memcached cluster.
As I know this functionality is not provided by default.
Hence as options - you may use CouchBase Server or something like Repcached.
Both of them has disadvantages: CouchBase Server is much slower
Dear memcached community,
It would be really good to build a failover memcached cluster.
As I know this functionality is not provided by default.
Hence as options - you may use CouchBase Server or something like
Repcachedhttp://sourceforge.net/projects/repcached/
.
Both of them has
Don't.
Consider your memcached nodes as defense for your database.
If you have N physical nodes in your single logical memcached cluster,
if one of the physical nodes goes away, then your database will have a
burst of 1/N additional activity until the data is re-balanced to the
remaining N-1
if what's you cache is not raw
result sets but post processed data.
Boris
On Tue, Mar 5, 2013 at 12:53 PM, Nelz nelz9...@gmail.com wrote:
Don't.
Consider your memcached nodes as defense for your database.
If you have N physical nodes in your single logical memcached cluster,
if one
On Wed, Oct 17, 2012 at 12:25 AM, Raymond Wang rmn...@gmail.com wrote:
I am newbie to Memcached, and I have a questions about cluster deployment:
does memcached support data synchronization betwean cluster nodes? if it
does, how can I determine the scope of synchronization?
No, the keys are
I am newbie to Memcached, and I have a questions about cluster deployment:
does memcached support data synchronization betwean cluster nodes? if it
does, how can I determine the scope of synchronization?
Thanks in advance.
Hi,
How to check the integrity of memcached cluster ? If not complete, we can
add the lack immediately.
Best Regards,
Jumping Qu
--
Don't tell me how many enemies we have, but where they are!
(ADV:Perl -- It's like Java, only it lets you deliver on time and under
budget.)
I'd just like to check that my understanding of how a distributed
memcached system works. Are these 2 assertions correct?
1) It's the client which is configured to know about multiple
memcached servers; the servers themselves know nothing about being
part of a cluster.
2) If you have one client
Assertion 1 is correct.
Assertion 2 and the answer to your two questions depends on the client and
the type of hashing they use to determine which server to use. To understand
this, check out the libketama consistent hash
3. There is not a single hashing algorithm defined for use by a
memcached client.
so
4. There is no guarantee that two clients with the same configured set
of servers, configured in the same order, will use the same server for
the same key.
If they use the same client software, they will
Hi Rachel,
For assertation 2, yes, it's a matter of chance which key is stored in which
server, but depending on which server selection algorithm you use, you can
determine the probability of a key being stored on the same server from both
clients. (It's higher if you use Ketama) Still, you
Thanks for your replies. So is this correct?
3. There is not a single hashing algorithm defined for use by a
memcached client.
so
4. There is no guarantee that two clients with the same configured set
of servers, configured in the same order, will use the same server for
the same key.
Rachel
26 matches
Mail list logo
