In practice, we rarely have issues with our Storm processes. We have Nimbus/supervisors that never restart for months. But when they do have issues, it's very nice to have them under supervision. Sometimes it's not even things under their control (e.g. OOM during high memory usage scenarios).
For development, there shouldn't be an issues foregoing supervision. Michael Rose (@Xorlev <https://twitter.com/xorlev>) Senior Platform Engineer, FullContact <http://www.fullcontact.com/> [email protected] On Fri, May 2, 2014 at 12:41 PM, P. Taylor Goetz <[email protected]> wrote: > I don’t think you need root to run supervisord: > > http://supervisord.org/running.html > > If you’re just testing something out, and don’t mind your cluster going > down, then running without supervision is okay. But I would NEVER suggest > someone run Storm’s daemons without supervision in a production environment. > > - Taylor > > On May 2, 2014, at 2:29 PM, Albert Chu <[email protected]> wrote: > > > I'm attempting to run Storm on a platform that I don't have root on. So > > I won't be able to run it under Redhat's supervisord that's already > > installed. > > > > How resilient are the Storm daemons by themselves? Are they reasonably > > resilient or are they programmed to not handle even relatively simple > > errors? > > > > I should probably say, this probably wouldn't be run in a production > > environment. Just trying to understand if the documentation writers are > > saying, "you should really do this for production" or "it won't work if > > you don't do this." > > > > Thanks, > > > > Al > > > > -- > > Albert Chu > > [email protected] > > Computer Scientist > > High Performance Systems Division > > Lawrence Livermore National Laboratory > > > > > >
