Date: Thu, 1 Nov 2012 21:21:51 -0700 (PDT)
From: Nick Saika <nicksa...@gmail.com>
To: redis-db@googlegroups.com
Message-Id: <f505606b-3932-40c9-a336-144fea1635c2@googlegroups.com>
In-Reply-To: <CAH=gea-WRoFzuQMcdckCxhzxPzPrPrF=xnDGY8=cVXRWe=41zg@mail.gmail.com>
References: <6bd2c07e-f869-4ac1-bac6-5f755af32052@googlegroups.com>
 <CAH=gea-WRoFzuQMcdckCxhzxPzPrPrF=xnDGY8=cVXRWe=41zg@mail.gmail.com>
Subject: Re: [ANN] Scarlet 0.6.0 - An HTTP interface for Redis
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_540_29190196.1351830111712"

------=_Part_540_29190196.1351830111712
Content-Type: multipart/alternative; 
	boundary="----=_Part_541_279118.1351830111712"

------=_Part_541_279118.1351830111712
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

To be perfectly honest, Michael, I am taking the approach of assuming there 
is no Sentinel; that being said though, I have to admit I haven't looked 
too much into Redis Sentinel, and I will definitely do that over my 
vacation, and see if I can leverage any of the feature(s) provided by 
Sentinel.

My initial plan for assisting with Redis' master-slave replication, was to 
build up a list of nodes in the chain via data gleaned from the INFO 
command. Should a master fail out, for any reason, Scarlet would elect one 
of that master's slaves to become the new master, and then update any of 
the old master's slaves to point to the new master. I haven't thought 
too-too far into this yet, but my initial thought would be to have the old 
master (once it comes alive again), to become a slave of the new master.

On Thursday, 1 November 2012 17:57:46 UTC-4, Michael Gorsuch wrote:
>
> Nick - thank you!  I love the idea of a Go frontend largely due to ease of 
> deployment (don't need to make sure a supporting runtime is installed).
>
> When you speak of replication setups, are you considering leveraging 
> sentinel here?
>
> Best,
>
> Michael Gorsuch
>
>
> On Thu, Nov 1, 2012 at 2:21 PM, Nick Saika <nick...@gmail.com<javascript:>
> > wrote:
>
>> In my spare time, I have been working on an HTTP frontend for Redis, 
>> written in Go: Scarlet <http://nesv.github.com/Scarlet/>. 
>>
>> Version 0.6.0 of Scarlet is the first version to be "fully-functional"; 
>> you can create, read, update and delete keys. Some of my future plans for 
>> Scarlet include:
>>
>>    - Providing clustering support 
>>    - Automatic failover for replication setups
>>    - A nice, web-based monitoring interface for your clustering and 
>>    replication setups
>>    - Act as a load-balancer in front of a cluster, including forwarding 
>>    all write operations to masters, and all read operations to slaves 
>>
>> If anyone is interested in trying it out, I would welcome any feedback!
>>
>> -- 
>> 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/-/8eyz24uB5OAJ.
>> To post to this group, send email to redi...@googlegroups.com<javascript:>
>> .
>> To unsubscribe from this group, send email to 
>> redis-db+u...@googlegroups.com <javascript:>.
>> For more options, visit this group at 
>> http://groups.google.com/group/redis-db?hl=en.
>>
>
>
------=_Part_541_279118.1351830111712
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

To be perfectly honest, Michael, I am taking the approach of assuming there=
 is no Sentinel; that being said though, I have to admit I haven't looked t=
oo much into Redis Sentinel, and I will definitely do that over my vacation=
, and see if I can leverage any of the feature(s) provided by Sentinel.<div=
><br></div><div>My initial plan for assisting with Redis' master-slave repl=
ication, was to build up a list of nodes in the chain via data gleaned from=
 the INFO command. Should a master fail out, for any reason, Scarlet would =
elect one of that master's slaves to become the new master, and then update=
 any of the old master's slaves to point to the new master. I haven't thoug=
ht too-too far into this yet, but my initial thought would be to have the o=
ld master (once it comes alive again), to become a slave of the new master.=
</div><div><br>On Thursday, 1 November 2012 17:57:46 UTC-4, Michael Gorsuch=
  wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0=
.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Nick - thank you! &nbs=
p;I love the idea of a Go frontend largely due to ease of deployment (don't=
 need to make sure a supporting runtime is installed).<div><br></div><div><=
div>When you speak of replication setups, are you considering leveraging se=
ntinel here?</div>
<div><br></div><div>Best,</div><div><br></div><div>Michael Gorsuch</div></d=
iv><div><br><br><div class=3D"gmail_quote">On Thu, Nov 1, 2012 at 2:21 PM, =
Nick Saika <span dir=3D"ltr">&lt;<a href=3D"javascript:" target=3D"_blank" =
gdf-obfuscated-mailto=3D"YLuPW6YgOGQJ">nick...@gmail.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">In my spare time, I have been working on an =
HTTP frontend for Redis, written in Go: <a href=3D"http://nesv.github.com/S=
carlet/" target=3D"_blank">Scarlet</a>.&nbsp;<div>
<br></div><div>Version 0.6.0 of Scarlet is the first version to be "fully-f=
unctional"; you can create, read, update and delete keys. Some of my future=
 plans for Scarlet include:</div><div><ul><li>Providing clustering support&=
nbsp;<br>
</li><li>Automatic failover for replication setups</li><li>A nice, web-base=
d monitoring interface for your clustering and replication setups</li><li>A=
ct as a load-balancer in front of a cluster, including forwarding all write=
 operations to masters, and all read operations to slaves</li>
</ul><div><span style=3D"line-height:17px">If anyone is interested in tryin=
g it out, I would welcome any feedback!</span></div></div><span><font color=
=3D"#888888">

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups "=
Redis DB" group.<br>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msg/redis-db/-/8eyz24uB5OAJ" target=3D"_blank">https://groups.google.c=
om/d/<wbr>msg/redis-db/-/8eyz24uB5OAJ</a>.<br>=20
To post to this group, send email to <a href=3D"javascript:" target=3D"_bla=
nk" gdf-obfuscated-mailto=3D"YLuPW6YgOGQJ">redi...@googlegroups.com</a>.<br=
>
To unsubscribe from this group, send email to <a href=3D"javascript:" targe=
t=3D"_blank" gdf-obfuscated-mailto=3D"YLuPW6YgOGQJ">redis-db+u...@<wbr>goog=
legroups.com</a>.<br>

For more options, visit this group at <a href=3D"http://groups.google.com/g=
roup/redis-db?hl=3Den" target=3D"_blank">http://groups.google.com/<wbr>grou=
p/redis-db?hl=3Den</a>.<br>


</font></span></blockquote></div><br></div>
</blockquote></div>
------=_Part_541_279118.1351830111712--

------=_Part_540_29190196.1351830111712--