<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question create by mistake worker duplicate node in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201957#M71714</link>
    <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;we create by mistake worker node (&lt;STRONG&gt; worker11&lt;/STRONG&gt; with datanode &amp;amp; namenode ) , while cluster already have &lt;STRONG&gt;worker11&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;only when we start the new &lt;STRONG&gt;worker11&lt;/STRONG&gt; we notice that other node - &lt;STRONG&gt;worker11&lt;/STRONG&gt; already exsist&lt;/P&gt;&lt;P&gt;so the problem is that we erased the OS of &lt;STRONG&gt;worker11&lt;/STRONG&gt; ( without delete it from the cluster )  , and new worker - &lt;STRONG&gt;worker11 &lt;/STRONG&gt;stay in the cluster&lt;/P&gt;&lt;P&gt;after couple hour we notice that heartbeat loses on the new &lt;STRONG&gt;worker11&lt;/STRONG&gt; and after some time&lt;STRONG&gt; worker11 &lt;/STRONG&gt;crash , so we need to start this machine ( boot ) again and so on&lt;/P&gt;&lt;P&gt;it is clear that all the problem on &lt;STRONG&gt;worker11 &lt;/STRONG&gt;are because this is duplicate machine , ( while the old &lt;STRONG&gt;worker11&lt;/STRONG&gt; machine was removed  from the VM center ( OS )&lt;/P&gt;&lt;P&gt;so what is the workaround to do on &lt;STRONG&gt;worker11&lt;/STRONG&gt; node ? , in ordeer amabri cluster will get this machine without problems?&lt;/P&gt;</description>
    <pubDate>Fri, 24 Nov 2017 20:42:18 GMT</pubDate>
    <dc:creator>mike_bronson7</dc:creator>
    <dc:date>2017-11-24T20:42:18Z</dc:date>
    <item>
      <title>create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201957#M71714</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;we create by mistake worker node (&lt;STRONG&gt; worker11&lt;/STRONG&gt; with datanode &amp;amp; namenode ) , while cluster already have &lt;STRONG&gt;worker11&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;only when we start the new &lt;STRONG&gt;worker11&lt;/STRONG&gt; we notice that other node - &lt;STRONG&gt;worker11&lt;/STRONG&gt; already exsist&lt;/P&gt;&lt;P&gt;so the problem is that we erased the OS of &lt;STRONG&gt;worker11&lt;/STRONG&gt; ( without delete it from the cluster )  , and new worker - &lt;STRONG&gt;worker11 &lt;/STRONG&gt;stay in the cluster&lt;/P&gt;&lt;P&gt;after couple hour we notice that heartbeat loses on the new &lt;STRONG&gt;worker11&lt;/STRONG&gt; and after some time&lt;STRONG&gt; worker11 &lt;/STRONG&gt;crash , so we need to start this machine ( boot ) again and so on&lt;/P&gt;&lt;P&gt;it is clear that all the problem on &lt;STRONG&gt;worker11 &lt;/STRONG&gt;are because this is duplicate machine , ( while the old &lt;STRONG&gt;worker11&lt;/STRONG&gt; machine was removed  from the VM center ( OS )&lt;/P&gt;&lt;P&gt;so what is the workaround to do on &lt;STRONG&gt;worker11&lt;/STRONG&gt; node ? , in ordeer amabri cluster will get this machine without problems?&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 20:42:18 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201957#M71714</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-24T20:42:18Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201958#M71715</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Usually "ambari-agent" starts sending the heartbeat messages to the ambari-server when it is started.&lt;/P&gt;&lt;P&gt;So if you do not want your old "worker11" not to send registration request to the Ambari-Server then please stop the ambari-agent on that host.  or remove the ambari-server hostname entry from the "/etc/ambari-agent/conf.ambari-agent.ini"  file of that particular agent.&lt;/P&gt;&lt;PRE&gt;# ambari-agent stop
# mv /etc/ambari-agent/confambari-agent.ini  /etc/ambari-agent/confambari-agent.ini.unwanted
# ambari-agent stop        (just to make sure that stop is already performed)&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;If above does not work then as an alternate option we might need to delete the Old worker11 host entry from the DataBase directly.&lt;BR /&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 20:50:09 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201958#M71715</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-11-24T20:50:09Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201959#M71716</link>
      <description>&lt;P&gt;hi Jay , the old worker11&lt;STRONG&gt; not exists any more&lt;/STRONG&gt; we removed the worker11 from the Vcenter - ( it was  VM machine ), so we cant do any steps on the old host , only we have the new worker11 &lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 21:00:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201959#M71716</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-24T21:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201960#M71717</link>
      <description>&lt;P&gt;@jay about "&lt;/P&gt;delete the Old worker11 host entry from the DataBase" , I guess need to do it on the ambari-server , if true please then show me the steps , or if needed some extra steps please let me know what are they ,</description>
      <pubDate>Fri, 24 Nov 2017 21:08:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201960#M71717</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-24T21:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201961#M71718</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;We can find the host_id of the unwanted Host from Ambari DB and delete those selected hosts.  (as we are making DB changes so please consider the risk and please collect the DB dump for backup)&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Step0). Please make sure to collect a latest ambari DB dump. (THis step is must so that we can revert back to rpeviosu stage).   **MUST DO**&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Step1). &lt;/STRONG&gt;Stop ambari-server.&lt;/P&gt;&lt;PRE&gt;# ambari-server stop&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;Step2).  &lt;/STRONG&gt;Please get their "host_id" of the unwanted host based on the hostname using the following SQL query.&lt;/P&gt;&lt;PRE&gt;select host_id from hosts where host_name='unwanted1.host.com';&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;Step3).  &lt;/STRONG&gt;Once using the above command we get the "host_id". then we know that the above host need to be deleted, So delete them as following: &lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;NOTE:&lt;/STRONG&gt; i am writing a dummy host_id as "999"  (dummy ID) in the following query, pelase replace it according to the previous query results. &lt;/P&gt;&lt;PRE&gt;delete from execution_command where task_id in (select task_id from host_role_command where host_id in (999));
delete from host_version where host_id in (999);
delete from host_role_command where host_id in (999);
delete from serviceconfighosts where host_id in (999);
delete from hoststate where host_id in (999);
delete from kerberos_principal_host WHERE host_id='unwanted1.host.com';  ----&amp;gt; For kerberized Env
delete from hosts where host_name in ('unwanted1.host.com');
delete from alert_current where history_id in ( select alert_id from alert_history where host_name in ('unwanted1.host.com'));&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;.&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Step4). &lt;/STRONG&gt;Start ambari Server&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;PRE&gt;# ambari-server start&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 21:28:52 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201961#M71718</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-11-24T21:28:52Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201962#M71719</link>
      <description>&lt;P&gt;Thank you  JAY , I will try it on Sunday since I am out of work now ,&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 21:40:33 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201962#M71719</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-24T21:40:33Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201963#M71720</link>
      <description>&lt;P&gt;Hi Jay , I just test the first command on my test ambari server machine ---&amp;gt; &lt;/P&gt;&lt;P&gt;# su postgres&lt;/P&gt;&lt;P&gt;
bash-4.2$ psql &lt;/P&gt;&lt;P&gt;postgres=# select host_id from hosts where host_name='worker11.sys67.com';&lt;/P&gt;&lt;P&gt;
ERROR:  relation "hosts" does not exist &lt;/P&gt;&lt;P&gt;LINE 1: select host_id from hosts where host_name='worker11.sys67...    , ( what is wrong here ? )&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 22:03:31 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201963#M71720</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-24T22:03:31Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201964#M71721</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If your ambari DB name is "ambari"  then you shoudl try this:&lt;/P&gt;&lt;PRE&gt;# psql -U ambari ambari
Enter Password: bigdata

ambari=&amp;gt;  select host_id from hosts where host_name='worker11.sys67.com';&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Nov 2017 01:41:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201964#M71721</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-11-25T01:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201965#M71722</link>
      <description>&lt;P&gt;@Jay , the old machine that was deleted and the new machine are with the same name ( worker11.sys55.com ) , so regarding to  the procedure "unwanted1.host.com"" , then it will effected also the new current machine , I mean the new machine will be effected also , &lt;/P&gt;</description>
      <pubDate>Sun, 26 Nov 2017 00:06:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201965#M71722</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-26T00:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201966#M71723</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The "hosts" table of ambari DB also shows the IP Address of the registered host.  So you should be able to find the difference between those two hosts. Also you can refer to other relevant tables like hostcomponentdesiredstate etc to differentiate between the hosts.&lt;BR /&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Sun, 26 Nov 2017 11:49:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201966#M71723</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-11-26T11:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: create by mistake worker duplicate node</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201967#M71724</link>
      <description>&lt;P&gt;@Jay , first thanks a lot for the great support , actually we solved it by re-configure the worker IP with the previous IP , and then restart the worker host , after server go's , data-node show alive on all workers and worker is part of the cluster  &lt;/P&gt;</description>
      <pubDate>Sun, 26 Nov 2017 21:14:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/create-by-mistake-worker-duplicate-node/m-p/201967#M71724</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2017-11-26T21:14:57Z</dc:date>
    </item>
  </channel>
</rss>

