You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Minying Lu (JIRA)" <ji...@apache.org> on 2015/06/27 18:31:04 UTC

[jira] [Created] (BIGTOP-1912) possible bug for spark-slave?

Minying Lu created BIGTOP-1912:
----------------------------------

             Summary: possible bug for spark-slave?
                 Key: BIGTOP-1912
                 URL: https://issues.apache.org/jira/browse/BIGTOP-1912
             Project: Bigtop
          Issue Type: Bug
          Components: vm
    Affects Versions: 0.8.0, backlog
         Environment: centos 6, openstack
            Reporter: Minying Lu


I saw this error when I'm running vagrant-puppet on openstack (see [BIGTOP-1911] for patch detail) 
Spark worked on master node, but not on slave node. It might be a puppet problem or a networking problem because spark randomly choose ports? The fact that it worked in master node made it looks like spark-master is doing some configuration for spark-slave and when in the slave node spark-master is not running, spark-slave breaks. 

I set /etc/hosts with ip address and fully domain name of the host 

{noformat}
==> hadoop-bigtop2: Error: Could not find resource 'Service[spark-master]' for relationship on 'Service[spark-worker]' on node hadoop-bigtop2.csail.mit.edu
==> hadoop-bigtop2: Error: Could not find resource 'Service[spark-master]' for relationship on 'Service[spark-worker]' on node hadoop-bigtop2.csail.mit.edu
An unknow error happened in Vagrant OpenStack provider
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)