NameNode and Standbynamenode auto stopped

[#1 · Accepted solution]

Hi,

I am able to telnet, ping to target machine and hostname.

It may be problem has resolved. Today HA NN in running state. I have done some changing. Let me share with you all.

1. First i have 3 three zookeeper server running. I had changed the zookeeper location from server 1 to server 4, meanwhile ha.zookeeper.quorum was still server1.zk.com:2181,server2.zk.com:2181,server3.zk.com:2181 even after restart all services.

I have changed it manually to server4.zk.com:2181,server2.zk.com:2181,server3.zk.com:2181.

2. Second i had done some modification in zookeeper configuration zoo.cfg

changed default to syncLimit=15, tickTime=4000 and initLimit=30.

Now it will take 15*4000=60sec to sync.

3. I have define the suggested properties in configuration files:

hdfs-site.xml

dfs.qjournal.start-segment.timeout.ms =90000
dfs.qjournal.select-input-streams.timeout.ms =90000
dfs.qjournal.write-txns.timeout.ms =90000

core-site.xml

ipc.client.connect.timeout =90000

4. All three JournalNode installed on Both Namenode instance and third installed on DataNode Server.

Today it seems everything is working fine.

[#2]

@Vinay K

@Sandeep Kumar

It's great that your problem has been resolved. It isn't normal that someone attributes himself the correct answer when other HCC members contributed to the answer namely Sandeep and I.

Your solution which was suggested by me.

1 Quorum of zookeeper 
3. Changes in the hdfs-site.xml/core-site.xml config 
4 Journal nodes /Sandeep too

So taking account the above I guess someone else merited the point :-)

[#3]

@Geoffrey Shelton

If you not comfort i can remove 2 point. I'd found 2nd point in zookeeper documentation.

[#4]

@Vinay K

Not important to me though but ethically . I am fine with all :-)

[#5]

@Geoffrey S. O.

May be that point is not meaningful.

Thanks for help me. You guys spent your precious time in community, That is appreciable.