Received: by 10.14.216.197 with SMTP id g45mr24049495eep.3.1351322338793;
        Sat, 27 Oct 2012 00:18:58 -0700 (PDT)
X-BeenThere: redis-db@googlegroups.com
Received: by 10.14.221.73 with SMTP id q49ls2474803eep.7.gmail; Sat, 27 Oct
 2012 00:18:34 -0700 (PDT)
Received: by 10.14.216.197 with SMTP id g45mr24048799eep.3.1351322314113;
        Sat, 27 Oct 2012 00:18:34 -0700 (PDT)
Received: by 10.14.216.197 with SMTP id g45mr24048798eep.3.1351322314105;
        Sat, 27 Oct 2012 00:18:34 -0700 (PDT)
Return-Path: <t...@lossen.de>
Received: from moutng.kundenserver.de (moutng.kundenserver.de. [212.227.17.10])
        by gmr-mx.google.com with ESMTPS id z47si815104eel.0.2012.10.27.00.18.33
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sat, 27 Oct 2012 00:18:34 -0700 (PDT)
Received-SPF: neutral (google.com: 212.227.17.10 is neither permitted nor denied by best guess record for domain of t...@lossen.de) client-ip=212.227.17.10;
Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 212.227.17.10 is neither permitted nor denied by best guess record for domain of t...@lossen.de) smtp.mail=...@lossen.de
Received: from [192.168.0.170] (g230122035.adsl.alicedsl.de [92.230.122.35])
	by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis)
	id 0LtnQD-1TK0PE2KuL-011hfV; Sat, 27 Oct 2012 09:18:33 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: redis swarm
From: Tim Lossen <t...@lossen.de>
In-Reply-To: <814d4d97-6a4b-4828-a282-6aa2a6bd24e2@googlegroups.com>
Date: Sat, 27 Oct 2012 09:18:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <01BEC454-4D20-4B74-A528-C4C0ECAAEDA2@lossen.de>
References: <E44FDE4A-0087-4152-A237-6D368153F03C@lossen.de> <814d4d97-6a4b-4828-a282-6aa2a6bd24e2@googlegroups.com>
To: redis-db@googlegroups.com
X-Mailer: Apple Mail (2.1084)
X-Provags-ID: V02:K0:RKA16aXBIcKwOmQsTU1YGBRxM2axfnz2uNZ7gOYVU0B
 ZZEvdqLV70ZDJHgRmdyVECoVO+e2IoQJFfgbfbVNVFDr4xWPNr
 nUM5ss083atEYsmYPdNsE++53eg2mL1zfV451GswzxJV7MuE1m
 wRBl4Y1reU5x7UD/7nYb8A5IRKW04Xo4eMqFrpNsgtn0jxsD21
 sGOmMUPUGOP5BrVLMusMW4x3K8jhpyaA9eDGkzzVw3WOTS1D25
 ySPyhm+raqtqiysmyuALHQRQpkUgofsvWloyZ1rR5QnX4stgXT
 iboU5V4OroDgkkQaWA4WXgn06OAZqRi7/oJlTAk2/z63p5eMKm
 tirBt0Wk5uRj7wlAWFTx9iT13cntYBruD5wYPsvz/

the basic idea is that each application server is self-contained. let's =
say we have five servers, each serving a fifth of the user population. =
if one goes down, 80% of users are not affected.

the expectation is that we will have *more* (but less severe) outages. =
of course it depends very much on the use case if this is a feasible =
strategy or not.


On 2012-10-26, at 18:21 , Jonathan Haddad wrote:

> I'm not sure what the advantage is of this over using redis w/ a =
master / slave setup.  Personally, I prefer to keep each machine =
dedicated to a particular task.  My web servers and my redis servers are =
logically different, thus live on different boxes.
>=20
> On Thursday, October 18, 2012 1:22:38 PM UTC-7, Tim Lossen wrote:
> hi all,=20
>=20
> i would like to share our current redis setup, which is slightly =
unusual.=20
>=20
> - redis is not the main datastore, but a cache for frequently used =
data, like highscore lists.=20
> - we have a cluster of application servers (currently 2, later =
probably around 8).=20
> - each server runs a local redis instance, and only ever talks to this =
instance.=20
> - cache writes are broadcast to all app servers via UDP over a private =
network, and then written to redis.=20
>=20
> this way, the whole redis swarm is always (more or less) in sync. the =
interesting point is that this setup is "masterless" -- any single =
instance can fail without affecting the others.=20
>=20
> sure, this does not offer the same consistency as redis cluster, but =
for some uses cases it is "good enough" -- while considerably simpler.=20=

>=20
> cheers=20
> tim=20
>=20
> --=20
> http://tim.lossen.de=20
>=20
> --=20
> You received this message because you are subscribed to the Google =
Groups "Redis DB" group.
> To view this discussion on the web visit =
https://groups.google.com/d/msg/redis-db/-/5BHu5DMrdeIJ.
> To post to this group, send email to redis-db@googlegroups.com.
> To unsubscribe from this group, send email to =
redis-db+unsubscribe@googlegroups.com.
> For more options, visit this group at =
http://groups.google.com/group/redis-db?hl=3Den.

--
http://tim.lossen.de