You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Zuocheng Ren (Created) (JIRA)" <ji...@apache.org> on 2012/03/26 21:52:27 UTC
[jira] [Created] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
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
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
[jira] [Commented] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
Posted by "Zuocheng Ren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238736#comment-13238736 ]
Zuocheng Ren commented on WHIRR-571:
------------------------------------
As mentioned by Andrei Savu, "it should be easy to fix: catch the NoSuchElementException in
Cluster.getInstancesMatching and return an empty set."
> 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
>
> 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
[jira] [Commented] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240327#comment-13240327 ]
Andrei Savu commented on WHIRR-571:
-----------------------------------
I've just tried the same recipe with 0.7.1 and I get the same exception you are seeing. The good news is that this issue is fixed in branch 0.7 and it's going to be part of the 0.7.2 release.
> 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
> Fix For: 0.7.2
>
> Attachments: exalt-hbase-ec2.properties, whirr.log
>
>
> 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
[jira] [Commented] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
Posted by "Zuocheng Ren (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239776#comment-13239776 ]
Zuocheng Ren commented on WHIRR-571:
------------------------------------
Sure.
I've attached my recipe to this issue.
The recipe attached will cause an exception during launching a cluster.
But if I add hadoop-jobtracker and hadoop-tasktracker, the cluster can start successfully.
BTW, I didn't make any change to the 0.7.1 release.
> 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
[jira] [Resolved] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
Posted by "Andrei Savu (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu resolved WHIRR-571.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.7.2
Marking as fixed in 0.7.2.
> 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
> Fix For: 0.7.2
>
> Attachments: exalt-hbase-ec2.properties, whirr.log
>
>
> 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
[jira] [Updated] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
Posted by "Zuocheng Ren (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zuocheng Ren updated WHIRR-571:
-------------------------------
Attachment: whirr.log
> 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, whirr.log
>
>
> 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
[jira] [Commented] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239453#comment-13239453 ]
Andrei Savu commented on WHIRR-571:
-----------------------------------
I am unable to reproduce this issue with trunk. I will also check with the 0.7 branch. Can you share your updated recipe? I was able to start a cluster running only HDFS (hadoop-namenode & hadoop-datanode) on aws-ec2.
> 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
>
> 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
[jira] [Commented] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239459#comment-13239459 ]
Andrei Savu commented on WHIRR-571:
-----------------------------------
HadoopConfigurationBuilder.java was not changed recently. Do you have local modifications or this is the standard release?
> 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
>
> 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
[jira] [Updated] (WHIRR-571) HadoopConfigurationBuilder assumes
that a Hadoop cluster has both a namenode and a jobtracker
Posted by "Zuocheng Ren (Updated) (JIRA)" <ji...@apache.org>.
[ 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