Member since
12-13-2016
12
Posts
7
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1767 | 03-21-2017 07:17 PM |
08-01-2017
08:26 PM
2 Kudos
Log4j settings Ambari uses sets of properties called Log4j properties to
control logging activities for each service running in your Hadoop cluster.
Initial, default values for each property reside in a <service_name>-log4j
template file. To access the default Log4j settings for a service; in
Ambari Web, you can browse to <Service_name> >
Configs > Advanced <service_name>-log4j. Often, user might want to configure the number of backup log
files or limit the maximum size of a log file. Prior to Ambari-2.5, this had to
be done by manually searching for the property in the log4j template Text Area
and modifying it. This is quite inconvenient. Ambari-2.4 and before Ambari-2.5 With Ambari-2.5, a simplified log rotation configuration
is provided i.e Log4j properties and values that limit the size and number of
backup log files for each service now appear above the log4j template file as
separate fields. Steps 1.Edit the values for the <service_name> backup
file size and <service_name> #
of backup files properties. 2.Click Save. Typically, once you modify these properties a restart
indicator shows up next to the relevant components. Restarting components in
the service pushes the configuration properties to each host running components
for that service. Fresh Install Ambari-2.5 These settings are readily available for any fresh install
of Ambari-2.5 Ambari 2.x
(x<5) Stack Upgrade These settings will be added during any stack upgrade. Ambari-2.x to Ambari-2.5 After upgrading Ambari from version 2.x to 2.5.0, if you
want to utilize the simplified log rotation configuration, you must update
configurations for all services in your cluster, using the following steps HDFS In Ambari Web, browse to HDFS > Configs > Advanced. Scroll down to Custom
HDFS-log4j. In Custom
HDFS-log4j, click Add Property. In Add Property,
type the following properties and values: hadoop_security_log_max_backup_size
= 256 hadoop_security_log_number_of_backup_files
= 20 hadoop_log_max_backup_size
= 256 hadoop_log_number_of_backup_files
= 10 Click Add. Browse to Advanced
hdfs-log4j . In Advanced
hdfs-log4j content section, find and replace the following
properties and values: Find: hadoop.security.log.maxfilesize=
<value>MB Replace: hadoop.security.log.maxfilesize={{hadoop_security_log_max_backup_size}}MB Find: hadoop.security.log.maxbackupindex=20 Replace: hadoop.security.log.maxbackupindex={{hadoop_security_log_number_of_backup_files}} Find: log4j.appender.RFA.MaxFileSize=<value>MB Replace: log4j.appender.RFA.MaxFileSize={{hadoop_log_max_backup_size}}MB Find: log4j.appender.RFA.MaxBackupIndex=<value> Replace: log4j.appender.RFA.MaxBackupIndex={{hadoop_log_number_of_backup_files}} In Configs,
click Save.Restart HDFS,
as prompted. For more information refer : https://docs.hortonworks.com/HDPDocuments/Ambari-2.5.1.0/bk_ambari-upgrade/content/upgrading_log_rotation_configuration.html
... View more
Labels:
07-24-2017
10:35 PM
Hi @Mustaquim Ulde, here is a nice article on upgrades - https://community.hortonworks.com/articles/2473/rolling-upgrade-express-upgrade-in-ambari.html
... View more
07-18-2017
09:37 PM
1 Kudo
Hi @Abhishek Kumar Do you have Storm in your cluster? Can you take a look at https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.1.0/bk_ambari-release-notes/content/ambari_relnotes-2.4.1.0-known-issues.html BUG-64959 You need to add the Ambari Server principal name to the Storm nimbus.admins property in Ambari Web > Services > Storm > Configs.
... View more
05-04-2017
05:42 PM
@Ahmed ELJAMI I see that your blueprint does not have such a property jdbc_jar_name. Can you please share the ambari-server logs as well? What is your ambari version? Can you also try "hive-env": { "hive_database": "Existing MySQL Database", replace with -> "Existing MySQL / MariaDB Database" Let me know if it works.
... View more
05-04-2017
12:27 AM
2 Kudos
Alternatively, you can also issue ambari-server reset and then run ambari-server setup
... View more
04-05-2017
04:54 PM
Hi Ahmed, I think there is an incorrect configuration attribute called jdbc_jar_name. You can try removing it and submitting the blueprint once more. If your blueprint isnt too large, maybe you can share it here.
... View more
03-24-2017
09:09 PM
You can also try by stopping the iptables/firewall....service iptables stop
... View more
03-23-2017
07:27 PM
Hi, Have you tried, ambari-server setup –j <path> -j JAVA_HOME, --java-home=JAVA_HOME
Use specified java_home. Must be valid on all hosts
... View more
03-21-2017
08:43 PM
1 Kudo
Sometimes when the iptables/firewalld is started, the UI doesnt open up. You can try stopping it and then accessing the UI to see if it works?
... View more
03-21-2017
08:10 PM
1 Kudo
Can you try systemctl stop firewalld
... View more