[ 
https://issues.apache.org/jira/browse/WHIRR-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zuocheng Ren updated WHIRR-571:
-------------------------------

    Attachment: exalt-hbase-ec2.properties
    
> HadoopConfigurationBuilder assumes that a Hadoop cluster has both a namenode 
> and a jobtracker
> ---------------------------------------------------------------------------------------------
>
>                 Key: WHIRR-571
>                 URL: https://issues.apache.org/jira/browse/WHIRR-571
>             Project: Whirr
>          Issue Type: Bug
>          Components: service/hadoop
>    Affects Versions: 0.7.1
>            Reporter: Zuocheng Ren
>            Priority: Trivial
>         Attachments: exalt-hbase-ec2.properties
>
>
> I removed hadoop-jobtracker and hadoop-tasktracker from 
> whirr.instance-templates in hbase-ec2.properties.
> Then I got the following error when trying to start a cluster.
> Am I doing anything wrong by removing the tracker from instance templates?
> Or is this an issue or not?
> If it is not an issue, am I be able to start hbase without starting the 
> jobtracker and tasktracker? What is the right way to do it?
> Authorizing firewall ingress to [us-east-1/i-98c4f0fc] on ports [50070] for 
> [128.83.158.52/32]
> Authorizing firewall ingress to [us-east-1/i-98c4f0fc] on ports [8020, 8021] 
> for [174.129.136.180/32]
> Unable to start the cluster. Terminating all nodes.
> java.util.NoSuchElementException
>       at 
> com.google.common.collect.AbstractIterator.next(AbstractIterator.java:152)
>       at 
> com.google.common.collect.Iterators.getOnlyElement(Iterators.java:293)
>       at 
> com.google.common.collect.Iterables.getOnlyElement(Iterables.java:265)
>       at org.apache.whirr.Cluster.getInstanceMatching(Cluster.java:171)
>       at 
> org.apache.whirr.service.hadoop.HadoopConfigurationBuilder.buildMapReduceConfiguration(HadoopConfigurationBuilder.java:135)
>       at 
> org.apache.whirr.service.hadoop.HadoopConfigurationBuilder.buildMapReduce(HadoopConfigurationBuilder.java:71)
>       at 
> org.apache.whirr.service.hadoop.HadoopClusterActionHandler.createHadoopConfigFiles(HadoopClusterActionHandler.java:104)
>       at 
> org.apache.whirr.service.hadoop.HadoopClusterActionHandler.beforeConfigure(HadoopClusterActionHandler.java:89)
>       at 
> org.apache.whirr.service.ClusterActionHandlerSupport.beforeAction(ClusterActionHandlerSupport.java:53)
>       at 
> org.apache.whirr.actions.ScriptBasedClusterAction.execute(ScriptBasedClusterAction.java:100)
>       at 
> org.apache.whirr.ClusterController.launchCluster(ClusterController.java:109)
>       at 
> org.apache.whirr.cli.command.LaunchClusterCommand.run(LaunchClusterCommand.java:63)
>       at org.apache.whirr.cli.Main.run(Main.java:64)
>       at org.apache.whirr.cli.Main.main(Main.java:97)
> Unable to load cluster state, assuming it has no running nodes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to