[
https://issues.apache.org/jira/browse/WHIRR-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461399#comment-13461399
]
Steve Loughran commented on WHIRR-663:
--------------------------------------
stack trace if you try it today
{code}
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)
{code}
> HadoopProxy to support clusters without a namenode
> --------------------------------------------------
>
> Key: WHIRR-663
> URL: https://issues.apache.org/jira/browse/WHIRR-663
> Project: Whirr
> Issue Type: Improvement
> Components: service/hadoop
> Affects Versions: 0.8.1
> Reporter: Steve Loughran
> Priority: Minor
>
> the Proxy setup code in {{HadoopProxy}} only works in clusters with
> namenodes, which works for Hadoop itself; services like Hama squeeze by.
> Clusters without a NameNode can't, and are reduced to copy-and-paste work.
> A good solution would be for core to have a proxy setup class; HadoopProxy
> would be just a NN-specific subclass
--
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
