thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: Strategies for continuous deployment of services to avoid interruption?
Date Tue, 01 Feb 2011 08:15:17 GMT
Yes.  But not like Erlang does.

Seriously, the problem is state, not code.  Typical server apps have a lot
of stuff cached which makes them run faster when warmed up.  A hot swap
doesn't provide that, really, even in Erlang.  Thus you need some pretty
fancy mechanisms including state replication and soft load reinstatement to
really handle hot swapping.

Take a look at Zookeeper for a system that manages to deal with hot swaps
and state.

On Tue, Feb 1, 2011 at 12:05 AM, Phillip B Oldham
<phillip.oldham@gmail.com>wrote:

> Would there be any way to do hot-code reloading, a bit like what Erlang
> does?
>
> On 25 January 2011 20:30, Ilya Maykov <ivmaykov@gmail.com> wrote:
> > It can be very tricky to detect failures in a distributed system. In
> fact, it's not always possible. Suppose your thrift RPC is just taking a
> really long time - at some point it will time out (based on some config
> parameter that you set). However the timeout is client-side and the server
> may have completed the request and was just about to respond when the client
> gave up. Or, maybe the request failed. Or maybe the server is still working
> on it. But, that discussion goes well beyond the scope of the original
> question in this thread :)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message