Member since
07-30-2019
453
Posts
112
Kudos Received
80
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1453 | 04-12-2023 08:58 PM | |
| 3452 | 04-04-2023 11:48 PM | |
| 1011 | 04-02-2023 10:24 PM | |
| 2655 | 07-05-2019 08:38 AM | |
| 2721 | 05-13-2019 06:21 AM |
02-05-2019
05:11 AM
Hi @Shraddha Singh, are you running the ambari-agent as root user ? and its given the sud opermission for : /usr/bin/ambari-python-wrap * is the below command running correctly when run manually? /usr/bin/hdp-select versions
... View more
01-29-2019
04:03 AM
Hi @abbas mohammadnejad , If you want ambari to use SSL for synching the LDAP , You should be reconfiguring the LDAP referring to https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-security/content/configure_ambari_to_use_ldap_server.html you can again run the command : ambari-server setup-ldap and Configure Accordingly.
... View more
01-29-2019
03:11 AM
Hi @Kumar Veerappan, I guess you are referring to this blog for Customizing the Ambari Alert : https://cwiki.apache.org/confluence/display/AMBARI/Customizing+the+Alert+Template then you can change the alert to Your desired one with help of editing the <subject></subject> in alert-templates.xml : https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/alert-templates.xml#L21 Just for example, I have some changes on subject for my Business logic : <subject>
<![CDATA[
#set( $criticalServices = $summary.getServicesByAlertState("CRITICAL"))
#if( $summary.getCriticalCount() ==0)
There is no new critical Alert!
#{else}
We have $summary.getCriticalCount() Critical Alert(s).Alert Details : ,#foreach( $service in $criticalServices ) #foreach( $alert in $summary.getAlerts($service,"CRITICAL") ) Service Name : $alert.getServiceName(),Host Name : $alert.getHostName()
#end
#end
#end
]]>
</subject> Which is doing nothing but Listing critical alert count in the Email subject. See if you can Makeuse of some thing out of it. Please give a Accept answer if it did.
... View more
01-08-2019
02:20 PM
Hi @Kunal Kumar, It looks like your add host operation is failing. Can you click on the hostname of failed host and see what is the error log saying. Also, I would like you to investigate if there is any clue on why it's failing with having a look on ambari-server logs when the operation is ongoing. tail -f /var/log/ambari-server/ambari-server.log Hope this helps.
... View more
01-02-2019
05:00 PM
1 Kudo
Hi @Oleg Khaykin ,
If your Cluster is managed by ambari then you are not supposed to edit the configs in the cluster manually.
you can perform the editing of configuration of your Hive service by logging into ambari-ui and clicking on Services -> Hive -> configs -> custom hive-site and edit the config as you require You can read more at
https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-operations/content/edit_advanced_config_properties.html
https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-operations/content/ch_Overview_hdp-ambari-user-guide.html
Please accept this answer if you found it helpful
... View more
12-31-2018
05:59 PM
Problem Statement : The hdfs encryption guide for HDP 3.0.1 states "In Ambari, replace the current value of dfs.permissions.superusergroup with the group name “operator”. however, this option is not available from Ambari. RootCause : As per fix of Apache bug : https://issues.apache.org/jira/browse/AMBARI-22086 ,ambari considers the dfs.permissions.superusergroup as a group property and by default the group property is not meant to be edited in ambari-ui. So the ui disabled the editing of this property by default. Workaround : Navigate to ambari-server and change this config via configs.py /var/lib/ambari-server/resources/scripts/configs.py -l <AMBARI_HOSTNAME>-t 8080-u <USER_NAME>-p <PASSWORD>-a <GET/SET/DELETE>-n <CLUSTER_NAME>-c <CONFIG_TYPE>-k <KEY>-v <VALUE>
For ex : [root@asnaik-asnaik1 ~]# /var/lib/ambari-server/resources/scripts/configs.py --help
Usage: configs.py [options]
Options:
-h, --help show this help message and exit
-t PORT, --port=PORT Optional port number for Ambari server. Default is
'8080'. Provide empty string to not use port.
-s PROTOCOL, --protocol=PROTOCOL
Optional support of SSL. Default protocol is 'http'
-a ACTION, --action=ACTION
Script action: <get>, <set>, <delete>
-l HOST, --host=HOST Server external host name
-n CLUSTER, --cluster=CLUSTER
Name given to cluster. Ex: 'c1'
-c CONFIG_TYPE, --config-type=CONFIG_TYPE
One of the various configuration types in Ambari. Ex:
core-site, hdfs-site, mapred-queue-acls, etc.
To specify credentials please use "-e" OR "-u" and "-p'":
-u USER, --user=USER
Optional user ID to use for authentication. Default is
'admin'
-p PASSWORD, --password=PASSWORD
Optional password to use for authentication. Default
is 'admin'
-e CREDENTIALS_FILE, --credentials-file=CREDENTIALS_FILE
Optional file with user credentials separated by new
line.
To specify property(s) please use "-f" OR "-k" and "-v'":
-f FILE, --file=FILE
File where entire configurations are saved to, or read
from. Supported extensions (.xml, .json>)
[root@asnaik-asnaik1 ~]# /var/lib/ambari-server/resources/scripts/configs.py -l asnaik1 -t 8080 -u admin -p admin -a set -n asnaik -c hdfs-site -k dfs.permissions.superusergroup -v hdfs,operator
2018-12-10 15:19:00,604 INFO ### Performing "set":
2018-12-10 15:19:00,604 INFO ### new property - "dfs.permissions.superusergroup":"hdfs,operator"
2018-12-10 15:19:00,663 INFO ### on (Site:hdfs-site, Tag:version1543379050314)
2018-12-10 15:19:00,675 INFO ### PUTting json into: doSet_version1544455140675467.json
2018-12-10 15:19:00,767 INFO ### NEW Site:hdfs-site, Tag:version1544455140675467
[root@asnaik-asnaik1 ~]# /var/lib/ambari-server/resources/scripts/configs.py -l asnaik1 -t 8080 -u admin -p admin -a get -n asnaik -c hdfs-site -k dfs.permissions.superusergroup |grep -i dfs.permissions.superusergroup
... View more
Labels:
12-31-2018
05:26 PM
Hi @Manjunath P N HDP-3.0.1 uses ambari-2.7.x versions and you should be aware of ambari-2.7.x behavioural changes here : https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/bhvr_changes_upgrade_hdp3_amb27.html Additionally, from HDP-3.x versions support for RHEL/CentOS/OEL 6, SLES 11, and Debian 7 have been removed, you must upgrade your underlying operating system before upgrade if it falls in unsupported version . referring to :
https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/upgrading_cluster_os.html
Support for Some of ambari views has been removed in HDP-3.0.1 , referring to :
https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/bhvr_changes_upgrade_hdp3_amb27.html
Also HDP-3.x upgrade only supports Express upgrade(no rolling upgrade ) , so you might plan for stopping the HDP services while upgrade. if you are using Hive , you must be in HDP-2.6.5 for smooth conversion of your hive tables .referring to :
https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade-ppc/content/prepare_hive_for_upgrade.html
Its always better to take Apache Ambari database backup, backup of your HDP services table and data before upgrade. If its a production cluster feel free to contact hortonworks support for limited upgrade program, details here : https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/ambari_upgrade_guide.html Refer to : https://supportmatrix.hortonworks.com for any compatability related clarifications And its always helpfull to perform a upgrade in development enviornment before upgrade in your production cluster Please login and accept this answer if you found this helpful.
... View more
12-29-2018
03:40 AM
Hey Jack, Very much glad that it worked. I have created an apache jira on this regard : https://issues.apache.org/jira/browse/AMBARI-25075 you can be yourself a jira watcher to this JIRA.
... View more
12-28-2018
04:23 PM
Hey @Nihal Shelke, Can you show me what exact change have you done referring to my previous comment . Is there any eror in hbase-master server out logs ? probably this might be due to some typo in the variable set. Will revert back the changes i mentioned make the hbase to run smoothly ?
... View more
12-28-2018
02:06 PM
2 Kudos
Problem statement : i am upgrading my ambari-2.6.2.2 to ambari-2.7.3 and the ambari-server upgrade commands fails with exception : java.sql.SQLSyntaxErrorException: Unknown table 'ambari_configuration' in information_schema [root@slambe-1 java]# ambari-server upgrade
Using python /usr/bin/python
Upgrading ambari-server
INFO: Upgrade Ambari Server
INFO: Updating Ambari Server properties in ambari.properties ...
INFO: Updating Ambari Server properties in ambari-env.sh ...
INFO: Original file ambari-env.sh kept
INFO: Fixing database objects owner
Ambari Server configured for MySQL. Confirm you have made a backup of the Ambari Server database [y/n] (n)? y
INFO: Upgrading database schema
ERROR: Unexpected ValueError: No JSON object could be decoded
For more info run ambari-server with -v or --verbose option when i see ambari-server logs i see the following exception: 2018-12-28 13:59:07,062 INFO [main] DBAccessorImpl:869 - Executing query: CREATE TABLE ambari_configuration (category_name VARCHAR(100) NOT NULL, property_name VARCHAR(100) NOT NULL, property_value VARCHAR(2048)) ENGINE=INNODB
2018-12-28 13:59:07,087 ERROR [main] SchemaUpgradeHelper:209 - Upgrade failed.
java.sql.SQLSyntaxErrorException: Unknown table 'ambari_configuration' in information_schema
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
at com.mysql.cj.jdbc.StatementImpl.executeQuery(StatementImpl.java:1218)
at com.mysql.cj.jdbc.DatabaseMetaData$7.forEach(DatabaseMetaData.java:2965)
at com.mysql.cj.jdbc.DatabaseMetaData$7.forEach(DatabaseMetaData.java:2953)
at com.mysql.cj.jdbc.IterateBlock.doForAll(IterateBlock.java:56)
at com.mysql.cj.jdbc.DatabaseMetaData.getPrimaryKeys(DatabaseMetaData.java:3006)
at org.apache.ambari.server.orm.DBAccessorImpl.tableHasPrimaryKey(DBAccessorImpl.java:1086)
at org.apache.ambari.server.orm.DBAccessorImpl.addPKConstraint(DBAccessorImpl.java:577)
at org.apache.ambari.server.orm.DBAccessorImpl.addPKConstraint(DBAccessorImpl.java:588)
at org.apache.ambari.server.upgrade.UpgradeCatalog270.addAmbariConfigurationTable(UpgradeCatalog270.java:989)
at org.apache.ambari.server.upgrade.UpgradeCatalog270.executeDDLUpdates(UpgradeCatalog270.java:319)
at org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:970)
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:207)
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
2018-12-28 13:59:07,093 ERROR [main] SchemaUpgradeHelper:475 - Exception occurred during upgrade, failed
org.apache.ambari.server.AmbariException: Unknown table 'ambari_configuration' in information_schema
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:210)
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
Caused by: java.sql.SQLSyntaxErrorException: Unknown table 'ambari_configuration' in information_schema
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) Root Cause : If you are facing the abouve exception while upgrading to ambari-2.7.0 versions the main reason will be mysql-connector.jar . Please upgrade to supported MySQL connector jar ,currently mysql-5.7 is supported version for ambari, please download connector that supports this version Please download the MYSQL Connector jar from url : https://dev.mysql.com/downloads/connector/j/5.1.html Download MYSQL connector 5.1.47 .jar from this url Change the the mysql-connector using the following docs : https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.3.0/administering-ambari/content/amb_using_hive_with_mysql.html and retry the ambari-server upgrade operation again. Please contact Hortonworks support if its a production cluster and you cannot do the steps of your own
... View more
Labels: