Member since
02-01-2017
4
Posts
1
Kudos Received
0
Solutions
02-07-2017
06:48 PM
@apappu many, many thanks again for your effort (your first answer helped me a lot to solve the issue on my side). @Jay SenSharma also many thanks for your detailed explanation and providing URLs to the latest Java sources. PS (to Jay SenSharma): I saw that the number of your "Reputation" credits are higher than those of apappu. Therefore I marked his first answer with "Accept". I hope you can live with it.
... View more
02-07-2017
01:10 PM
1 Kudo
@apappu Additional question (because of these findings in the ambari-server.log file): ls5567:~ # grep ambari-client-thread /var/log/ambari-server/ambari-server.log 07 Feb 2017 12:10:47,371 WARN [main] AmbariServer:693 - The configured Jetty ambari-client-thread thread pool value of 25 is not sufficient on a host with 80 processors. Increasing the value to 60. 07 Feb 2017 12:10:47,372 INFO [main] AmbariServer:701 - Jetty is configuring ambari-client-thread with 40 reserved acceptors/selectors and a total pool size of 60 for 80 processors. What is the relationship between client.threadpool.size.max and agent.threadpool.size.max values ? - client.threadpool.size.max <= or < agent.threadpool.size.max ? - client.threadpool.size.max >= or > agent.threadpool.size.max ? - client.threadpool.size.max = agent.threadpool.size.max ?
... View more
02-07-2017
07:20 AM
@apappu many thanks: increasing the value of parameter agent.threadpool.size.max did it.
do you have any "rule-of-thumb" or "best-practice" formula at hand to what minimum size this value should be set ?
... View more
02-06-2017
06:33 PM
Problem:
Runtime issue of a "fresh" Ambari server for SLES 11.4 installation (see http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-installation/content/ch_Installing_Ambari.html). There is no communication between Ambari Server and Ambari Agent via handshake or registration/heartbeat ports. A connection to the port can be established on client-side but there is no server-side response from the application listening on the port.
curl shows "TLSv1.0, TLS handshake, Client hello (1)" only (answer "TLSv1.0, TLS handshake, Server hello (1)" is missing):
ls5567:~ # curl -v https://localhost:8440;
* About to connect() to localhost port 8440 (#0)
* Trying 127.0.0.1... connected
* Connected to localhost (127.0.0.1) port 8440 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* TLSv1.0, TLS handshake, Client hello (1):
* SSL connection timeout
* Closing connection #0
curl: (28) SSL connection timeout
openssl hangs forever:
ls5567:~ # openssl s_client -connect localhost:8440
CONNECTED(00000003)
^C
netstat reports this:
ls5567:~ # netstat -nopa|grep :844
tcp 0 0 127.0.0.1:49634 127.0.0.1:8440 ESTABLISHED 62178/openssl off (0.00/0/0)
tcp 0 0 127.0.0.1:44860 127.0.0.1:8440 ESTABLISHED 36869/python off (0.00/0/0)
tcp 0 0 :::8440 :::* LISTEN 61747/java off (0.00/0/0)
tcp 0 0 :::8441 :::* LISTEN 61747/java off (0.00/0/0)
tcp 0 0 :::8443 :::* LISTEN 61747/java off (0.00/0/0)
tcp 137 0 127.0.0.1:8440 127.0.0.1:48270 CLOSE_WAIT 61747/java off (0.00/0/0)
tcp 137 0 127.0.0.1:8440 127.0.0.1:55292 CLOSE_WAIT 61747/java off (0.00/0/0)
tcp 128 0 127.0.0.1:8440 127.0.0.1:49634 ESTABLISHED 61747/java off (0.00/0/0)
tcp 128 0 127.0.0.1:8440 127.0.0.1:44860 ESTABLISHED 61747/java off (0.00/0/0)
Please share ideas to find the root cause of this issue.
... View more
Labels:
- Labels:
-
Apache Ambari