Chris Mattmann wrote:
One thing I noticed is that on my linux cluster, the additional options "-o ConnectTimeout=1 -o SendEnv=HADOOP_CONF_DIR" are not available on my system.
You can override this by editing conf/hadoop-env.sh. Both are optional, but convenient. Perhaps we should avoid using them until they're in wider distribution.
Here is the output of ssh -V on my system: [EMAIL PROTECTED] ~/hadoop]$ ssh -V OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
I run Ubuntu Breezy and have OpenSSH 4.1. I don't know what version of OpenSSH these features were added in.
Any ideas? Additionally, would it make sense to put in options within the startup script to only start DFS related daemons and slaves, and the same goes for only starting MapRed daemons and slaves? If so, I can create a JIRA issue about this.
Instead of 'bin/start-all.sh' that's just 'bin/hadoop-daemon.sh start namenode; bin/hadoop-daemons.sh start datanode'. Is that what you're after? I guess we could add a bin/start-dfs.sh command that does this.
Doug
