You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Kevin W Monroe (JIRA)" <ji...@apache.org> on 2017/05/10 17:25:04 UTC
[jira] [Created] (BIGTOP-2765) fix roles logic for spark/zeppelin
charms
Kevin W Monroe created BIGTOP-2765:
--------------------------------------
Summary: fix roles logic for spark/zeppelin charms
Key: BIGTOP-2765
URL: https://issues.apache.org/jira/browse/BIGTOP-2765
Project: Bigtop
Issue Type: Bug
Components: deployment
Affects Versions: 1.2.0
Reporter: Kevin W Monroe
Assignee: Kevin W Monroe
Priority: Minor
Fix For: 1.2.1
The spark charm always includes the spark-worker role and also includes spark-master on the leader unit. This is not valid when spark is in yarn-* mode. There is no need for master/worker processes to be running when spark is in yarn mode.
The zeppelin charm needs spark-datanucleus because the included spark bits are tightly coupled to hive. We manually apt install this package, but we should be using an appropriate role to leverage bigtop puppet just like we do for the spark charm. This only affects deployments *without* a separate spark unit, but that is a valid use case and we should have a nice UX for people that only deploy zeppelin.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)