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 |
02-16-2020
10:32 PM
@Kureikana Can you try this Suppose you start your infra solr process as "infra-solr" user then try the following command. Non Kerberos Env: # su - infra-solr
# source /etc/ambari-infra-solr/conf/infra-solr-env.sh
# /usr/lib/ambari-infra-solr/bin/solr start -cloud -noprompt -s /var/lib/ambari-infra-solr/data 2>&1 Kerberos Env: # su - infra-solr
# kinit -kt /etc/security/keytabs/ambari-infra-solr.service.keytab <AMBARI_INFRA_PRINCIPAL>
# source /etc/ambari-infra-solr/conf/infra-solr-env.sh
# /usr/lib/ambari-infra-solr/bin/solr start -cloud -noprompt -s /var/lib/ambari-infra-solr/data -Dsolr.kerberos.name.rules='DEFAULT' 2>&1 .
... View more
02-13-2020
02:23 PM
@AarifAkhter We see the error is cause by some DB access/connect Caused by: java.lang.RuntimeException: Error while creating database accessor
at org.apache.ambari.server.orm.DBAccessorImpl.<init>(DBAccessorImpl.java:120) So few queries: 1. Is this a newly setup ambari server? 2. Do you see the DataBase is running fine and the DB host/port is accessible ? 3. Are you using Embedded Postgres Database? 4. When was last time ambari server running fine? Any recent chances made to ambari server config/host ? I am suspecting that there should be some more detailed log like some more "Caused By" section in your ambari-server.log which is not copied fully in your last update. So can you please recheck your ambari log and let us know what was the first error and if you can share the Full stack trace. some times there are more than on "Caused By" section in a single stack trace.
... View more
02-12-2020
04:26 PM
Hi @lwang @jsensharma Thank you for the useful information that you've provided. After doing some testing. I found out that there an issue with one of the network interfaces on the servers. By testing the jumbo frame connectivity. We remove the defective module and heartbeat lost has been resolved. Thank you for your assistance guys!.
... View more
02-10-2020
06:57 AM
I have found a solution. I have forgot to mention that before service is in Maintenance Mode. To perform action with service in Maintenance Mode, it is needed to use one more parameter in rest API call. This article helped me describes all extra parameters.
... View more
02-05-2020
10:33 PM
@gvbnn Those are just warnings you can ignore them ... it should not be causing Job failure. As we also see that the application_id "application_1580968178673_0001" is also generated ... So you should be able to check the status of your Yarn application in ResourceManagr UI. http://$RM_ADDRESS:8088/cluster/apps If your cluster has enough resources then you should see the progress as well for your application_id ...
... View more
02-04-2020
04:06 AM
Thanks You
... View more
02-03-2020
11:42 PM
Set the value of the dfs.webhdfs.enabled property in hdfs-site.xml to true. <property>
<name>dfs.webhdfs.enabled</name>
<value>true</value>
</property> Create an HTTP service user principal. kadmin: addprinc -randkey HTTP/$<Fully_Qualified_Domain_Name>@$<Realm_Name>.COM where: Fully_Qualified_Domain_Name: Host where the NameNode is deployed. Realm_Name: Name of your Kerberos realm. Create a keytab file for the HTTP principal. kadmin: xst -norandkey -k /etc/security/spnego.service.keytab HTTP/$<Fully_Qualified_Domain_Name> Verify that the keytab file and the principal are associated with the correct service. klist –k -t /etc/security/spnego.service.keytab Add the dfs.web.authentication.kerberos.principal and dfs.web.authentication.kerberos.keytab properties to hdfs-site.xml. <property>
<name>dfs.web.authentication.kerberos.principal</name>
<value>HTTP/$<Fully_Qualified_Domain_Name>@$<Realm_Name>.COM</value>
</property>
<property>
<name>dfs.web.authentication.kerberos.keytab</name>
<value>/etc/security/spnego.service.keytab</value>
</property> Restart the NameNode and the DataNodes.
... View more
02-03-2020
01:28 PM
1 Kudo
Dear Jay what to say excellent answer , you are really one of the best here
... View more
01-30-2020
08:04 PM
Dear Jay finally we found the issue it was about the mistake in /etc/hosts file instead of 127.0.0.1 , it was the ip address - 27.0.0.1 so we fix it and restart the postgresql and ambari now all are fine
... View more