Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2823 | 04-27-2020 03:48 AM | |
| 5475 | 04-26-2020 06:18 PM | |
| 4643 | 04-26-2020 06:05 PM | |
| 3699 | 04-13-2020 08:53 PM | |
| 5602 | 03-31-2020 02:10 AM |
01-03-2019
12:33 AM
1 Kudo
@Dan Dan Can you check the host by running the NetCat comant to findout if the HDFS user is able to bind to port 50070 where you are getting the "java.net.BindException: Port in use: ec2-34-211-154-113.us-west-2.compute.amazonaws.com:50070" error? You can use netcat command to attempt binding port 50070 using "hdfs" user as following: (If any other process is using that port then you should see "Address already in use" message in the output. # su - hdfs
# nc -l ec2-34-211-154-113.us-west-2.compute.amazonaws.com 50070 Check the output of the above command to see if you get any message saying "Address already in use. QUITTING." ? (if yes then find the PID of thast process and then kill it)
... View more
01-02-2019
09:10 AM
@Michael Bronson We can find the AMS collector Mode by looking at the "ams-site.xml" file. # grep -A1 'mode' /etc/ambari-metrics-collector/conf/ams-site.xml
<name>timeline.metrics.service.operation.mode</name>
<value>embedded</value><br> If AMS is running in Embedded mode and you are keep getting the same Zookeeper error then better to try increasing the AMS collector Heap size to 2GB or more (like 4GB) and then try starting it again. Please try increasing the heap setting for HBase Master Heapsize as well. For AMS tuning it is best to refer to the following article. https://community.hortonworks.com/content/supportkb/208353/troubleshooting-ambari-metrics-ams.html
... View more
01-02-2019
08:29 AM
@Michael Bronson Your
current Thread query looks very similar to the other HCC thread opened
by you: https://community.hortonworks.com/questions/231177/metrics-failed-on-orgapachehadoophbasezookeeperzoo.html?childToView=232247#answer-232247 . Can you please mark one of the HCC thread as Closed so that all the hcc users can respond to the same single thread.
... View more
01-02-2019
08:19 AM
@Michael Bronson Your current Thread query looks very similar to the other HCC thread opened by you: https://community.hortonworks.com/questions/231176/metrics-collector-ams-hbase-unsecure-received-unex.html?childToView=232246#answer-232246 . Can you please mark one of the HCC thread as Closed so that all the hcc users can respond to the same single thread.
... View more
01-02-2019
08:16 AM
1 Kudo
@Michael Bronson Can you please share the complete AMS collector logs .. along with the HMaster log which you can find in the same directory where the AMS collector log is present. Do you have enough free memory available on your system (where AMS is running) Also can you please share the cluster node numbers present in your cluster? based on that we can try to find if the Heap settings for AMS collector and HMaster are OK or not? Also let us know if your AMS collector is running in Embedded Mode or Distributed Mode? Looking at collector-gc.log and gc.log (fopr hmaster process can be also good). What is the Ambari Version and the output of the following command (Any recent ambari upgrade performed recently?) When was the AMS running fine last time? Any recent changes made to ams configs? # rpm -qa | grep ambari .
... View more
01-01-2019
12:40 AM
@Weiss Ruth This HCC thread looks duplicate of another one. As per HCC recommendations for the same issue please open only one thread so that all the relevant answers can be found on one thread. https://community.hortonworks.com/questions/232181/sign-in-with-root-user.html?childToView=232212#answer-232212 . Copying my response from other thread: Please make sure that you are using the correct SSH port to connect
to the Sandbox. The port will be 2222 something like following: # ssh root@127.0.0.1 -p 2222
Enter password : hadoop . Or you can also use the Web Client to do SSH login to sandbox like by accessing the following URL. http://localhost:4200
... View more
12-14-2018
05:11 AM
Sometimes it is desired to see what kind of Http request ambari server makes to the outside works for troubleshooting purpose and to know the value of various http headers (like: User-Agent, Accept, Last-Modified, Content-Type, Content-Length, Connection, ETag, Server, X-Cache ...etc) which ambari-server uses to make calls to Ambari Public repo ...etc. So in order to achieve the Http Logging of ambari server made http requests we can do the following: Step-1). Create a file "/etc/ambari-server/conf/http.logging.properties" with the following content: .level=INFO
handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=ALL
sun.net.www.protocol.level=ALL
sun.net.www.protocol.http.HttpURLConnection.level=ALL
debug.level=ALL . Step-2). Inside the "/var/lib/ambari-server/ambari-env.sh" file variable "AMBARI_JVM_ARGS" make sure to add the following parameter "-Djava.util.logging.config.file=/etc/ambari-server/conf/http.logging.properties" to enable the http logging. Example: export AMBARI_JVM_ARGS="$AMBARI_JVM_ARGS -Xms512m -Xmx2048m -XX:MaxPermSize=128m -Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -Dcom.sun.jndi.ldap.connect.pool.protocol=\"plain ssl\" -Dcom.sun.jndi.ldap.connect.pool.maxsize=20 -Dcom.sun.jndi.ldap.connect.pool.timeout=300000 -Djava.util.logging.config.file=/etc/ambari-server/conf/http.logging.properties" . Step-3). Restart Ambari Server. # ambari-server restart . Step-4). Now check the "/var/log/ambari-server/ambari-server.out" file to see the http logging. Example Output: Dec 14, 2018 4:52:29 AM sun.net.www.protocol.http.HttpURLConnection plainConnect0
FINEST: ProxySelector Request for http://public-repo-1.hortonworks.com/HDP/ubuntu14/3.x/updates/3.0.0.0/HDP-3.0.0.0-1634.xml
Dec 14, 2018 4:52:29 AM sun.net.www.http.HttpClient logFinest
FINEST: KeepAlive stream retrieved from the cache, sun.net.www.http.HttpClient(http://public-repo-1.hortonworks.com/HDP/centos7/3.x/updates/3.0.0.0/HDP-3.0.0.0-1634.xml)
Dec 14, 2018 4:52:29 AM sun.net.www.protocol.http.HttpURLConnection plainConnect0
FINEST: Proxy used: DIRECT
Dec 14, 2018 4:52:29 AM sun.net.www.protocol.http.HttpURLConnection writeRequests
FINE: sun.net.www.MessageHeader@5b3d7d395 pairs: {GET /HDP/ubuntu14/3.x/updates/3.0.0.0/HDP-3.0.0.0-1634.xml HTTP/1.1: null}{User-Agent: Java/1.8.0_112}{Host: public-repo-1.hortonworks.com}{Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2}{Connection: keep-alive}
Dec 14, 2018 4:52:29 AM sun.net.www.http.HttpClient logFinest
FINEST: KeepAlive stream used: http://public-repo-1.hortonworks.com/HDP/ubuntu14/3.x/updates/3.0.0.0/HDP-3.0.0.0-1634.xml
Dec 14, 2018 4:52:29 AM sun.net.www.protocol.http.HttpURLConnection getInputStream0
FINE: sun.net.www.MessageHeader@7854dac13 pairs: {null: HTTP/1.1 200 OK}{Content-Type: application/xml}{Content-Length: 2597}{Connection: keep-alive}{Last-Modified: Thu, 12 Jul 2018 23:45:36 GMT}{Accept-Ranges: bytes}{Server: AmazonS3}{Date: Thu, 13 Dec 2018 12:28:28 GMT}{ETag: "abcdefgh42ffdc96d0ab1de61e0dc36cd3"}{Age: 59042}{X-Cache: Hit from cloudfront}{Via: 1.1 frontend_cloud.example.net (CloudFront)}{X-Amz-Cf-Id: Sn-ABCDEFGH8xvcOmkqoeHg_UCYmwyRU9tgDonWfAd4TMXoPdMabcdefgh==}
Dec 14, 2018 4:52:29 AM sun.net.www.protocol.http.HttpURLConnection plainConnect0
FINEST: ProxySelector Request for http://public-repo-1.hortonworks.com/HDP/centos7-ppc/3.x/updates/3.0.0.0/HDP-3.0.0.0-1634.xml
Dec 14, 2018 4:52:29 AM sun.net.www.http.HttpClient logFinest
FINEST: KeepAlive stream retrieved from the cache, sun.net.www.http.HttpClient(http://public-repo-1.hortonworks.com/HDP/ubuntu14/3.x/updates/3.0.0.0/HDP-3.0.0.0-1634.xml)
Dec 14, 2018 4:52:29 AM sun.net.www.protocol.http.HttpURLConnection plainConnect0
FINEST: Proxy used: DIRECT
Dec 14, 2018 4:52:29 AM sun.net.www.protocol.http.HttpURLConnection writeRequests
FINE: sun.net.www.MessageHeader@32b9674a5 pairs: {GET /HDP/centos7-ppc/3.x/updates/3.0.0.0/HDP-3.0.0.0-1634.xml HTTP/1.1: null}{User-Agent: Java/1.8.0_112}{Host: public-repo-1.hortonworks.com}{Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2}{Connection: keep-alive}
Dec 14, 2018 4:52:29 AM sun.net.www.http.HttpClient logFinest
FINEST: KeepAlive stream used: http://public-repo-1.hortonworks.com/HDP/centos7-ppc/3.x/updates/3.0.0.0/HDP-3.0.0.0-1634.xml
Dec 14, 2018 4:52:29 AM sun.net.www.protocol.http.HttpURLConnection getInputStream0
FINE: sun.net.www.MessageHeader@606955ef13 pairs: {null: HTTP/1.1 200 OK}{Content-Type: application/xml}{Content-Length: 2609}{Connection: keep-alive}{Date: Mon, 10 Dec 2018 09:44:35 GMT}{Last-Modified: Fri, 13 Jul 2018 04:43:55 GMT}{ETag: "abcdefgh42ffdc96d0ab1de61e0dc36cd3"}{Accept-Ranges: bytes}{Server: AmazonS3}{Age: 59042}{X-Cache: Hit from cloudfront}{Via: 1.1 frontend_cloud.example.net (CloudFront)}{X-Amz-Cf-Id: ABCDEFGHb3LeLucDbVt5BgHNJmhZRjQPUYPMZS7zHO7oqR1Kabcdefgh==}
.
... View more
Labels:
11-15-2018
03:26 AM
When we access an HDFS directory using Ambari FileView then we see max 5000 sub directories/contents per page via File View. As following: We see a message "Showing 5000 files or folders of xxxx". The default "views.files.max.files.per.page" limit is set to 5000 as following: /ambari/view/commons/hdfs/FileOperationService.java#L53-L56 This property was added from Ambari 2.6 as part of JIRA: https://issues.apache.org/jira/browse/AMBARI-21890 to avoid browser hung state while opening a HDFS folder which has huge number of files. So if user wants to see more items per page then it can be achieved as following: 1. In order to set/add a new property with the value with a bit large page size please adjust the following property inside "ambari.properties". For example i am setting it to 7000 # grep 'views.files.max.files.per.page' /etc/ambari-server/conf/ambari.properties
views.files.max.files.per.page=7000 2. Then restart the Ambari Server. # ambari-server restart 3. Once ambari server is restarted then check the File View again to verify if it is showing the mentioned number of per pages or not? 4. After accessing the File View directories we should also see the ambari-server.log the pagination value reflected properly or not? # grep 'maxFilesPerPageProperty' /var/log/ambari-server/ambari-server.log
INFO [ambari-client-thread-38] FileOperationService:69 - maxFilesPerPageProperty = 7000 .
... View more
Labels:
10-15-2018
10:10 PM
@Ivan Georgiev Thank you for sharing the parameter.
... View more
09-12-2018
09:55 AM
@Jonathan Sneep Wonderful Article !!!
... View more