Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2329
@jongyoul What is your current design and plan ? Since this is a big
change, it might be better to reach consensus on the design, otherwise it would
waste your time if we found issue after you complete the implementation.
Overall, I have 2 concerns and suggestions:
1. use spark-submit to launch spark's InterpreterProcess instead of using
yarn api to do that. Because using yarn api means to reinvent the wheel of
spark's yarn module, and it would take lots of time to keep the behavior
consistent with spark yarn module as there's many tricky things and
configurations
2. How to specify the port when launching the InterpreterProcess in yarn
cluster mode. I mentioned it in ZEPPELIN-2035, as I think we need to finish
ZEPPELIN-2035 first.
---
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.
---
