[
https://issues.apache.org/jira/browse/WHIRR-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457043#comment-13457043
]
Steve Loughran commented on WHIRR-655:
--------------------------------------
and a {{jps -v}} of the destination machine shows that part of it has come up,
but it's now in a very odd state with DFSAdmin running alongside the NN (and
not terminating)
{code}
jps -v
23435 NameNode -Dproc_namenode -Xmx1000m -Djava.net.preferIPv4Stack=true
-Dhadoop.log.dir=/var/log/hadoop/logs
-Dhadoop.log.file=hadoop-hadoop-namenode-hdp1.cotham.uk.log
-Dhadoop.home.dir=/usr/lib/hadoop/libexec/.. -Dhadoop.id.str=hadoop
-Dhadoop.root.logger=INFO,DRFA -Dhadoop.security.logger=INFO,DRFAS
-Djava.library.path=/usr/lib/hadoop/libexec/../lib/native/Linux-amd64-64
-Dhadoop.policy.file=hadoop-policy.xml
1918 Jps -Dapplication.home=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64
-Xms8m
23727 DFSAdmin -Dproc_dfsadmin -Xmx1000m -Djava.net.preferIPv4Stack=true
-Dhadoop.log.dir=/var/log/hadoop/logs -Dhadoop.log.file=hadoop.log
-Dhadoop.home.dir=/usr/lib/hadoop/libexec/.. -Dhadoop.id.str=
-Dhadoop.root.logger=INFO,console -Dhadoop.security.logger=INFO,NullAppender
-Djava.library.path=/usr/lib/hadoop/libexec/../lib/native/Linux-amd64-64
-Dhadoop.policy.file=hadoop-policy.xml
{code}
> installations can time out on slow networks -timeout needs to be configurable
> -----------------------------------------------------------------------------
>
> Key: WHIRR-655
> URL: https://issues.apache.org/jira/browse/WHIRR-655
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.9.0
> Environment: cable connection; first yum install of a set of
> artifacts hosted on S3
> Reporter: Steve Loughran
> Priority: Minor
>
> Downloading RPMs from a yum repo over a slow link can take so long that
> scripts start to time out & your systems are left in an indeterminate state.
> It ought to be possible to specify timeouts on a per-cluster basis.
--
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
