As Taylor said you can indeed run Storm via supervisord under a non-root user.
The only thing to keep in mind off the top of my head is that there are a couple of root-only supervisord configuration options/features that won't work if you run supervisord as an unprivileged user. That being said none of those root-only features would be required for running Storm. (Also: If you're on RHEL6 then your supervisord version is most likely very outdated, i.e. 2.x. Keep that in mind when you browse the docs on supervisord.org, which cover 3.x.) If it's a development environment then you don't really need supervisord at all, just like Taylor and Michael already said. --Michael On 02.05.2014 20:41, P. Taylor Goetz 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 >> >> >
