Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2034
Yes, agreed, documentation is one part, but, other part being how should
Zeppelin or `RemoteInterpreterProcess` handle connection is more important.
So, in the same example as describe above where livy's default mode is `per
user`, and here "admin-grp" goes and changes some setting say mode from
"yarn-cluster" to "yarn-client" (a hypothetical example) saves setting and
restart. Now in current implementation, except for this user others that
connected to livy's server before this user "admin" are still submitting to
"yarn-cluster", which to me is wrong; because the source of truth should have
been Zeppelin's interpreter setting page, new the users that were connected to
this interpreter before this change are behaving different, and new users will
behave different.
So, IMHO until we have individual interpreter setting for individual user
(or we support the scenario described above
https://github.com/apache/zeppelin/pull/2034#issuecomment-280888650); whenever
restart or edit and saved is clicked, all processes should terminate.
Let me know what you think, and any other thought that I might be missing ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
