Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.7.0
-
None
Description
When master and worker components are deployed to the same node it is important to guarantee the sequence of startup events: e.g worker will fail if master isn't present. Currently, this is a limitation of the Spark implementation where a worker doesn't wait for master to start up and fails immediately.
Also, the master service only has to be started on the master node.
Attachments
Attachments
Issue Links
- relates to
-
BIGTOP-1260 Puppet deployment should reflect on the new name of spark package
- Resolved