You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@thrift.apache.org by Samoilov <sa...@gmail.com> on 2014/05/28 02:52:02 UTC

uninterrupted update for thrift based service

Greetings,
We are building v1 version of our service that will implement Thrift
interface. The service must run uninterruptedly even during update (e.g. we
update from v1 to v2). I want to avoid updates based on port (run v1 on
port1 and v2 on port2) as this makes updates pretty complicated. One of the
ideas to try SO_REUSEPORT option with socket. I see that (THRIFT-2034)
provides access to socket. But too late - after bind. May be there is a
better option for uninterrupted update? Or somebody already knows that
SO_REUSEPORT will not work.

Thank you,
Denis

Re: uninterrupted update for thrift based service

Posted by Samoilov <sa...@gmail.com>.
James, thank you!
we plan to run our service on thousands of our web frontends and I want to
avoid deploying HAProxy at the moment.


On Tue, May 27, 2014 at 5:54 PM, James Haggerty <mu...@gmail.com> wrote:

> We run thrift servers behind haproxy so we can easily switch things around.
>
>
> On Wed, May 28, 2014 at 10:52 AM, Samoilov <sa...@gmail.com> wrote:
>
> > Greetings,
> > We are building v1 version of our service that will implement Thrift
> > interface. The service must run uninterruptedly even during update (e.g.
> we
> > update from v1 to v2). I want to avoid updates based on port (run v1 on
> > port1 and v2 on port2) as this makes updates pretty complicated. One of
> the
> > ideas to try SO_REUSEPORT option with socket. I see that (THRIFT-2034)
> > provides access to socket. But too late - after bind. May be there is a
> > better option for uninterrupted update? Or somebody already knows that
> > SO_REUSEPORT will not work.
> >
> > Thank you,
> > Denis
> >
>

Re: uninterrupted update for thrift based service

Posted by James Haggerty <mu...@gmail.com>.
We run thrift servers behind haproxy so we can easily switch things around.


On Wed, May 28, 2014 at 10:52 AM, Samoilov <sa...@gmail.com> wrote:

> Greetings,
> We are building v1 version of our service that will implement Thrift
> interface. The service must run uninterruptedly even during update (e.g. we
> update from v1 to v2). I want to avoid updates based on port (run v1 on
> port1 and v2 on port2) as this makes updates pretty complicated. One of the
> ideas to try SO_REUSEPORT option with socket. I see that (THRIFT-2034)
> provides access to socket. But too late - after bind. May be there is a
> better option for uninterrupted update? Or somebody already knows that
> SO_REUSEPORT will not work.
>
> Thank you,
> Denis
>