Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Storm Multi Tenancy - Best practices

avatar

I've got a customer who is going to have multiple storm topology running ( different business area ) on top of a single cluster. What's the best way to guarantee multi-tenancy? ( they are not using Slider )

Thanks,

Olivier

1 ACCEPTED SOLUTION

avatar

Storm multi tenancy can be enabled when using security only. In non-secure mode all worker jvms will be running as user "storm" as a single user. Where as in storm secure mode (using kerberos) you can set supervisor.worker.run.as.user to true. This makes worker jvm to run as user who submitted the topology. This will give worker isolation between topologies.

More details

https://github.com/apache/storm/blob/master/SECURITY.md#run-worker-processes-as-user-who-submitted-t...

View solution in original post

2 REPLIES 2

avatar
Master Mentor

@olivier

This may help to go into the right direction.

Also, found this on slideshare

Hope this helps.

avatar

Storm multi tenancy can be enabled when using security only. In non-secure mode all worker jvms will be running as user "storm" as a single user. Where as in storm secure mode (using kerberos) you can set supervisor.worker.run.as.user to true. This makes worker jvm to run as user who submitted the topology. This will give worker isolation between topologies.

More details

https://github.com/apache/storm/blob/master/SECURITY.md#run-worker-processes-as-user-who-submitted-t...