Member since
08-08-2017
1652
Posts
30
Kudos Received
11
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1921 | 06-15-2020 05:23 AM | |
| 15482 | 01-30-2020 08:04 PM | |
| 2074 | 07-07-2019 09:06 PM | |
| 8121 | 01-27-2018 10:17 PM | |
| 4571 | 12-31-2017 10:12 PM |
12-04-2017
11:31 AM
# host master01 master01.sys4.com has address 103.114.28.13 # host master03 master03.sys4.com has address 103.114.28.12
... View more
12-04-2017
11:28 AM
we get that: hdfs haadmin -failover -forceactive master01 master03
Illegal argument: Unable to determine service address for namenode 'master01'
... View more
12-04-2017
11:10 AM
in our ambari cluster both name node are like standby in order to force one of them to be active we do hdfs haadmin -transitionToActive --forceactive master01
Illegal argument: Unable to determine service address for namenode 'master01' but we get - Unable to determine service address what this is indicate ? and how to fix this issue ?
... View more
Labels:
- Labels:
-
Apache Ambari
-
Apache Hadoop
12-03-2017
11:00 PM
from the out file we get that --> Getting jmx metrics from NN failed. URL: http://master03.sys56.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
... View more
12-03-2017
07:59 PM
we have 3 masters machine in ambari cluster the first service that need to start is the zookeper server on all masters ( master01/02/03 ) but zookeeper service not start on the master01 and master02 machines from /var/log/zookeper we see the following : what chould be the problem ? 2017-12-03 19:54:29,832 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /120.14.51.19:59808
2017-12-03 19:54:29,838 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868] - Client attempting to establish new session at /120.14.51.19:59808
2017-12-03 19:54:29,844 - INFO [CommitProcessor:1:ZooKeeperServer@617] - Established session 0x1601dccc7e8049d with negotiated timeout 30000 for client /120.14.51.19:59808
2017-12-03 19:54:31,394 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of stream exception
EndOfStreamException: Unable to read additional data from client sessionid 0x1601dccc7e8049d, likely client has closed socket
at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
at java.lang.Thread.run(Thread.java:745)
2017-12-03 19:54:31,395 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1008] - Closed socket connection for client /120.14.51.19:59808 which had sessionid 0x1601dccc7e8049d
2017-12-03 19:54:33,474 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /120.14.51.19:59810
2017-12-03 19:54:33,482 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868] - Client attempting to establish new session at /120.14.51.19:59810
2017-12-03 19:54:33,492 - INFO [CommitProcessor:1:ZooKeeperServer@617] - Established session 0x1601dccc7e8049e with negotiated timeout 30000 for client /120.14.51.19:59810
2017-12-03 19:54:35,150 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of stream exception
EndOfStreamException: Unable to read additional data from client sessionid 0x1601dccc7e8049e, likely client has closed socket
at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
at java.lang.Thread.run(Thread.java:745)
2017-12-03 19:54:35,151 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1008] - Closed socket connection for client /120.14.51.19:59810 which had sessionid 0x1601dccc7e8049e
2017-12-03 19:54:35,378 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /120.14.51.17:50721
2017-12-03 19:54:35,388 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868] - Client attempting to establish new session at /120.14.51.17:50721
2017-12-03 19:54:35,397 - INFO [CommitProcessor:1:ZooKeeperServer@617] - Established session 0x1601dccc7e8049f with negotiated timeout 30000 for client /120.14.51.17:50721
^C
... View more
Labels:
- Labels:
-
Apache Ambari
12-03-2017
05:32 PM
we have ambari cluster version 2.6 , this ambari cluster configured with service auto start enabled for all the services in our cluster we stop all services as HDFS , YARN , Zookeeper . Hive , etc and reboot the masters machines ( master01,master02,master03 ) we suppose to get the services up after reboot , all machines linux are up include ambari-server and ambari-agent on all masters machines but all services are down include ZK , HDFS , YARN and all restt we not understand why the ambari feature - service auto start not start auto the services after boot ? how to know if service auto start is working here ? and how top trace it ? after one hour from the reboot still all services are down !
... View more
Labels:
- Labels:
-
Apache Ambari
-
Apache Hadoop
12-03-2017
02:26 PM
Wק can abort the deletion by running the following command in zookeeper: rmr /admin/delete_topics/gtom.poli.pri.procis Note that this will only prevent the deletion to proceed if it has not already started. If anything has already been deleted, it's gone
... View more
12-03-2017
08:53 AM
just in case we delete the wrong topic as /usr/hdp/current/kafka-broker/bin/kafka-topics.sh --zookeeper hdpmaster01:2181 --delete --topic gtom.poli.pri.proc
Topic gtom.poli.pri.procis already marked for deletion and now we want to revert it what are the steps to revert topic deletion? all folders topics as the following are still exists under /var/kafka/kafka-logs gtom.poli.pri.procis-23
gtom.poli.pri.procis-45
gtom.poli.pri.procis-34 . .
... View more
Labels:
- Labels:
-
Apache Ambari
-
Apache Hadoop
-
Apache Kafka
12-02-2017
11:04 PM
thank you for the answer , but we create another new worker machine instead that machine , I think it was waste of time find the problem on that machine and better to create a new one
... View more