Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2721
I'm not an expert of Supervisor V2 but just based on my understanding of
this issue, I guess we may want to address this to two different situations:
1. `supervisor.run.worker.as.user` is set
Supervisor should check the process with `worker` account (can be read via
worker state).
2. `supervisor.run.worker.as.user` is unset
Supervisor should check the process with `supervisor` account, as workers
will be always launched with `supervisor` account.
In any cases, if the worker is running with different account, it might be
considered as wrong process or out of sync. Ideally I think it should be
corrected (kill the process) but it might open security issue (account A
editing pid file for worker A1 and let Supervisor kill arbitrary process
running with other account) so error or critical log message might be a best
bet.
I'm not sure how many cases we can encounter above case, but unless the
hole is huge, I guess checking with above logic would work.
@arunmahadevan @revans2 Please correct me if I'm missing here and/or
there's better way to handle this.
---
