I created a yarn service manually to test the installation (No HA). After
that the service yarn was deleted.
A new yarn service by name yarn1 was created (HA), all is fine, un till I
ran a wordcount job from the CLI of one of the hadoop servers (hadoop jar
Hadoop-WordCount/wordcount.jar WordCount /user/wordcount/input
/user/wordcount/output). The job never starts and keeps trying the connect
to the fist yarn instance which is in standby.
Looking into client config that is created under /etc/hadoop it was still
pointing to the old yarn instance which was deleted and not to yarn1
I then manually rewired the symlink of hadoop-conf to
/etc/hadoop/conf.cloudera.yarn1 on all the hosts. After which the job ran
successfully and i was able to toggle between standby and active RM.
But, the problem now is that when ever I deploy client configuration or run
my cloudera install script that does the configuration deployment, it
reverts the symlink to the yarn instance and not yarn1.
Can anyone help?
lrwxrwxrwx. 1 root root 29 Apr 24 04:34 conf ->
drwxr-xr-x. 2 root root 4096 Apr 24 04:33 conf.cloudera.hdfs1
drwxr-xr-x. 2 root root 4096 Apr 17 18:32 conf.cloudera.mapreduce1
drwxr-xr-x. 2 root root 4096 Apr 23 23:05* conf.cloudera.yarn*
drwxr-xr-x. 2 root root 4096 Apr 24 04:33 *conf.cloudera.yarn1*
lrwxrwxrwx. 1 root root 59 Apr 23 23:57 hadoop ->
lrwxrwxrwx. 1 root root 64 Apr 23 23:57 hadoop-0.20 ->
lrwxrwxrwx. 1 root root 30 Apr 24 03:56 *hadoop-conf ->
lrwxrwxrwx. 1 root root 68 Apr 23 23:57 hadoop-fuse-dfs ->
lrwxrwxrwx. 1 root root 77 Apr 23 23:57 hadoop-httpfs-conf ->
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.