You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@thrift.apache.org by Kim Gustafson <ki...@eye.fi> on 2010/06/25 20:12:32 UTC
Thrift services and init
Hello, I am researching Thrift as a possible cross-language rpc mechanism, particularly between php on the front-end client and perl on the back-end service. I am curious what people are doing to make sure their thrift services start at boot and restart if they die.
As far as start at boot, I could put a new script in /etc/init.d (we are using CentOS) for each service. It seems a little cumbersome, requiring a more complicated release process for each new service introduced, but straightforward enough. The init.d scripts don't handle restart, which led me to research supervisord and runit.
Curious what others are doing or if there are any suggestions for mechanisms to research.
Thanks,
Kim Gustafson
Eye-Fi
Re: Thrift services and init
Posted by Pierre-Alexandre St-Jean <pa...@stjean.me>.
You could look into god.
http://god.rubyforge.org/
For startin services at boot you should use what your os uses. You can tough look into upstart which can integrate with init scripts.
Envoyé de mon iPhone
Le 2010-06-25 à 14:12, Kim Gustafson <ki...@eye.fi> a écrit :
> Hello, I am researching Thrift as a possible cross-language rpc mechanism, particularly between php on the front-end client and perl on the back-end service. I am curious what people are doing to make sure their thrift services start at boot and restart if they die.
>
> As far as start at boot, I could put a new script in /etc/init.d (we are using CentOS) for each service. It seems a little cumbersome, requiring a more complicated release process for each new service introduced, but straightforward enough. The init.d scripts don't handle restart, which led me to research supervisord and runit.
>
> Curious what others are doing or if there are any suggestions for mechanisms to research.
>
>
> Thanks,
>
> Kim Gustafson
> Eye-Fi
>
Re: Thrift services and init
Posted by Francisco Byun <co...@gmail.com>.
for launchd, I think the address is moved to
http://launchd.macosforge.org/ instead.
2010/6/26 Anner van Hardenbroek <dw...@gmail.com>:
> You can also look at launchd.
> http://launchd.macosforge.net/
>
> Bye,
>
> --
> Anner van Hardenbroek
>
> On 25 jun. 2010, at 20:17, Francisco Byun <co...@gmail.com> wrote:
>
>> Have you ever tried working with "supervisord"?
>>
>> http://supervisord.org/
>>
>> It is written in python, which aims to control Unix (Linux) program.
>> I'm involved with a project which uses Thrift for its back-end
>> service, and supervisord successfully restarts the back-end service
>> whenever it die.
>>
>> 2010/6/26 Kim Gustafson <ki...@eye.fi>:
>>> Hello, I am researching Thrift as a possible cross-language rpc mechanism, particularly between php on the front-end client and perl on the back-end service. I am curious what people are doing to make sure their thrift services start at boot and restart if they die.
>>>
>>> As far as start at boot, I could put a new script in /etc/init.d (we are using CentOS) for each service. It seems a little cumbersome, requiring a more complicated release process for each new service introduced, but straightforward enough. The init.d scripts don't handle restart, which led me to research supervisord and runit.
>>>
>>> Curious what others are doing or if there are any suggestions for mechanisms to research.
>>>
>>>
>>> Thanks,
>>>
>>> Kim Gustafson
>>> Eye-Fi
>>>
>>>
>
Re: Thrift services and init
Posted by Anner van Hardenbroek <dw...@gmail.com>.
You can also look at launchd.
http://launchd.macosforge.net/
Bye,
--
Anner van Hardenbroek
On 25 jun. 2010, at 20:17, Francisco Byun <co...@gmail.com> wrote:
> Have you ever tried working with "supervisord"?
>
> http://supervisord.org/
>
> It is written in python, which aims to control Unix (Linux) program.
> I'm involved with a project which uses Thrift for its back-end
> service, and supervisord successfully restarts the back-end service
> whenever it die.
>
> 2010/6/26 Kim Gustafson <ki...@eye.fi>:
>> Hello, I am researching Thrift as a possible cross-language rpc mechanism, particularly between php on the front-end client and perl on the back-end service. I am curious what people are doing to make sure their thrift services start at boot and restart if they die.
>>
>> As far as start at boot, I could put a new script in /etc/init.d (we are using CentOS) for each service. It seems a little cumbersome, requiring a more complicated release process for each new service introduced, but straightforward enough. The init.d scripts don't handle restart, which led me to research supervisord and runit.
>>
>> Curious what others are doing or if there are any suggestions for mechanisms to research.
>>
>>
>> Thanks,
>>
>> Kim Gustafson
>> Eye-Fi
>>
>>
Re: Thrift services and init
Posted by Francisco Byun <co...@gmail.com>.
Have you ever tried working with "supervisord"?
http://supervisord.org/
It is written in python, which aims to control Unix (Linux) program.
I'm involved with a project which uses Thrift for its back-end
service, and supervisord successfully restarts the back-end service
whenever it die.
2010/6/26 Kim Gustafson <ki...@eye.fi>:
> Hello, I am researching Thrift as a possible cross-language rpc mechanism, particularly between php on the front-end client and perl on the back-end service. I am curious what people are doing to make sure their thrift services start at boot and restart if they die.
>
> As far as start at boot, I could put a new script in /etc/init.d (we are using CentOS) for each service. It seems a little cumbersome, requiring a more complicated release process for each new service introduced, but straightforward enough. The init.d scripts don't handle restart, which led me to research supervisord and runit.
>
> Curious what others are doing or if there are any suggestions for mechanisms to research.
>
>
> Thanks,
>
> Kim Gustafson
> Eye-Fi
>
>
Re: Thrift services and init
Posted by Kevin Bombino <ke...@bombino.org>.
> As far as start at boot, I could put a new script in /etc/init.d (we are using CentOS) for each service. It seems a little cumbersome, requiring a more complicated release process for each new service introduced, but straightforward enough. The init.d scripts don't handle restart, which led me to research supervisord and runit
We use daemontools (http://cr.yp.to/daemontools.html) to supervise our
Thrift services and it works great. Though, you tend to either love it
or hate it.
Kevin Bombino // VerbCMS
http://verbcms.com/