-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow topologies to be executed as specific users #43
Comments
This relates to extensive efforts in storm-0.10.0+ to have user-specific topologies via "storm authentication": |
I'm not planning to work on this. |
@fuji-151a & @JessicaLHartog : FYI, this relates to PR #195. Please take note of @pdread100's initial comment about the user for the Supervisor and Logviewer. Since the launching of Logviewer is not supported by me in this project (not until STORM-1342 is fixed!), I don't particularly care about that part of it. And considering the Supervisor -- I don't see a problem with it being the same user as the workers. |
Notably, the idea with this issue was I think to not only allow the storm processes to run as a non-root user, but also to be able to allow different topologies to have different users. That would be a further enhancement beyond the change proposed to #195. I suppose it could be a Topology-specific configuration option, similar to the |
I agree. |
@fuji-151a : gotcha. Please give us a bit of time to merge the proposed change in #195, I wanna test it myself first. |
Some users want the option of running their topologies as a specific user. This on the surface would be easy to do by setting the FrameworkInfo.setUser() to that user. However that would force the Supervisor and LogViewer (PR) to run as that user as well. There may be scenarios where this is not advisable.
It appears that if CommandInfo.setUser() is set then the supervisor/topologies will be run as that user. I know mesos/myriad has gone through extensive coding to get this right, including chown of the installation directories.
The text was updated successfully, but these errors were encountered: