You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2012/09/12 18:52:07 UTC
[jira] [Created] (WHIRR-652) NoSuchElementException if you try to
deploy a JT in a cluster without an NN
Steve Loughran created WHIRR-652:
------------------------------------
Summary: NoSuchElementException if you try to deploy a JT in a cluster without an NN
Key: WHIRR-652
URL: https://issues.apache.org/jira/browse/WHIRR-652
Project: Whirr
Issue Type: Bug
Components: service/hadoop
Affects Versions: 0.9.0
Environment: BYON + Hadoop 1.0.3
Reporter: Steve Loughran
Priority: Minor
Trying to deploy a JT without an NN results in a failure (probably the right option) -but it doesn't get there until everything else has been done, and pops up with a stack trace
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-652) NoSuchElementException if you try to
deploy a JT in a cluster without an NN
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454121#comment-13454121 ]
Steve Loughran commented on WHIRR-652:
--------------------------------------
Steps to replicate:
{code}
whirr.instance-templates=1 hadoop-jobtracker
{code}
> NoSuchElementException if you try to deploy a JT in a cluster without an NN
> ---------------------------------------------------------------------------
>
> Key: WHIRR-652
> URL: https://issues.apache.org/jira/browse/WHIRR-652
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.9.0
> Environment: BYON + Hadoop 1.0.3
> Reporter: Steve Loughran
> Priority: Minor
>
> Trying to deploy a JT without an NN results in a failure (probably the right option) -but it doesn't get there until everything else has been done, and pops up with a stack trace
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-652) NoSuchElementException if you try to
deploy a JT in a cluster without an NN
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454120#comment-13454120 ]
Steve Loughran commented on WHIRR-652:
--------------------------------------
Looking at the log, it was after install and before configure, which makes sense. The stack trace isn't that helpful though.
> NoSuchElementException if you try to deploy a JT in a cluster without an NN
> ---------------------------------------------------------------------------
>
> Key: WHIRR-652
> URL: https://issues.apache.org/jira/browse/WHIRR-652
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.9.0
> Environment: BYON + Hadoop 1.0.3
> Reporter: Steve Loughran
> Priority: Minor
>
> Trying to deploy a JT without an NN results in a failure (probably the right option) -but it doesn't get there until everything else has been done, and pops up with a stack trace
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-652) NoSuchElementException if you try to
deploy a JT in a cluster without an NN
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454820#comment-13454820 ]
Tom White commented on WHIRR-652:
---------------------------------
It's possible to run a NN without a JT (this was done as a part of the work for YARN in WHIRR-391), but the other way round has not been tested.
It's certainly reasoanble to run a JT without a NN. I think the fix is relatively simple - make the second rule configuration in HadoopJobTrackerClusterActionHandler.doBeforeConfigure check if a NN can be found before opening the port.
> NoSuchElementException if you try to deploy a JT in a cluster without an NN
> ---------------------------------------------------------------------------
>
> Key: WHIRR-652
> URL: https://issues.apache.org/jira/browse/WHIRR-652
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.9.0
> Environment: BYON + Hadoop 1.0.3
> Reporter: Steve Loughran
> Priority: Minor
>
> Trying to deploy a JT without an NN results in a failure (probably the right option) -but it doesn't get there until everything else has been done, and pops up with a stack trace
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WHIRR-652) NoSuchElementException if you try to
deploy a JT in a cluster without an NN
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454118#comment-13454118 ]
Steve Loughran commented on WHIRR-652:
--------------------------------------
{code}
, exitStatus=0}
Wrote instances file /Users/stevel/.whirr/hadoop/instances
*CRITICAL* the cluster failed to launch and the automated node termination option was not selected, there might be orphaned nodes.
java.util.NoSuchElementException
at com.google.common.collect.AbstractIterator.next(AbstractIterator.java:154)
at com.google.common.collect.Iterators.getOnlyElement(Iterators.java:360)
at com.google.common.collect.Iterables.getOnlyElement(Iterables.java:270)
at org.apache.whirr.Cluster.getInstanceMatching(Cluster.java:186)
at org.apache.whirr.service.hadoop.HadoopCluster.getNamenodePublicAddress(HadoopCluster.java:39)
at org.apache.whirr.service.hadoop.HadoopJobTrackerClusterActionHandler.doBeforeConfigure(HadoopJobTrackerClusterActionHandler.java:51)
at org.apache.whirr.service.hadoop.HadoopClusterActionHandler.beforeConfigure(HadoopClusterActionHandler.java:101)
at org.apache.whirr.service.ClusterActionHandlerSupport.beforeAction(ClusterActionHandlerSupport.java:54)
at org.apache.whirr.actions.ScriptBasedClusterAction.execute(ScriptBasedClusterAction.java:118)
at org.apache.whirr.ByonClusterController.configureServices(ByonClusterController.java:99)
at org.apache.whirr.ClusterController.configureServices(ClusterController.java:153)
at org.apache.whirr.ClusterController.launchCluster(ClusterController.java:114)
at org.apache.whirr.cli.command.LaunchClusterCommand.run(LaunchClusterCommand.java:69)
at org.apache.whirr.cli.command.LaunchClusterCommand.run(LaunchClusterCommand.java:59)
at org.apache.whirr.cli.Main.run(Main.java:69)
at org.apache.whirr.cli.Main.main(Main.java:102)
Exception in thread "main" java.lang.RuntimeException: java.util.NoSuchElementException
at org.apache.whirr.ClusterController.launchCluster(ClusterController.java:128)
at org.apache.whirr.cli.command.LaunchClusterCommand.run(LaunchClusterCommand.java:69)
at org.apache.whirr.cli.command.LaunchClusterCommand.run(LaunchClusterCommand.java:59)
at org.apache.whirr.cli.Main.run(Main.java:69)
at org.apache.whirr.cli.Main.main(Main.java:102)
Caused by: java.util.NoSuchElementException
at com.google.common.collect.AbstractIterator.next(AbstractIterator.java:154)
at com.google.common.collect.Iterators.getOnlyElement(Iterators.java:360)
at com.google.common.collect.Iterables.getOnlyElement(Iterables.java:270)
at org.apache.whirr.Cluster.getInstanceMatching(Cluster.java:186)
at org.apache.whirr.service.hadoop.HadoopCluster.getNamenodePublicAddress(HadoopCluster.java:39)
at org.apache.whirr.service.hadoop.HadoopJobTrackerClusterActionHandler.doBeforeConfigure(HadoopJobTrackerClusterActionHandler.java:51)
at org.apache.whirr.service.hadoop.HadoopClusterActionHandler.beforeConfigure(HadoopClusterActionHandler.java:101)
at org.apache.whirr.service.ClusterActionHandlerSupport.beforeAction(ClusterActionHandlerSupport.java:54)
at org.apache.whirr.actions.ScriptBasedClusterAction.execute(ScriptBasedClusterAction.java:118)
at org.apache.whirr.ByonClusterController.configureServices(ByonClusterController.java:99)
at org.apache.whirr.ClusterController.configureServices(ClusterController.java:153)
at org.apache.whirr.ClusterController.launchCluster(ClusterController.java:114)
... 4 more
{code}
> NoSuchElementException if you try to deploy a JT in a cluster without an NN
> ---------------------------------------------------------------------------
>
> Key: WHIRR-652
> URL: https://issues.apache.org/jira/browse/WHIRR-652
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.9.0
> Environment: BYON + Hadoop 1.0.3
> Reporter: Steve Loughran
> Priority: Minor
>
> Trying to deploy a JT without an NN results in a failure (probably the right option) -but it doesn't get there until everything else has been done, and pops up with a stack trace
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira