Member since
09-30-2015
39
Posts
71
Kudos Received
9
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
806 | 11-15-2017 06:41 PM | |
1382 | 06-23-2017 07:30 AM | |
913 | 10-07-2016 03:45 AM | |
1129 | 10-04-2016 06:32 PM | |
1461 | 08-09-2016 11:09 AM |
10-04-2016
06:32 PM
1 Kudo
@Saurabh Looks like the HDP-UTILS repo path is incorrect. I see an additonal "/hdp/" in your path The UTILS repo for CentOS6 is at: http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.20/repos/centos6 The UTILS tar file is at: http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.20/repos/centos6/HDP-UTILS-1.1.0.20-centos6.tar.gz Check this link for more
... View more
09-12-2016
05:23 AM
Great article @Alejandro Fernandez Have added more details about the pre-checks here - https://community.hortonworks.com/articles/54944/stack-upgrade-pre-checks-purpose-and-remediation.html
... View more
09-05-2016
11:25 PM
5 Kudos
Cluster upgrade is a well-planned maintenance activity.
Before starting the upgrade, it is important to ensure that your cluster is
ready for upgrade. Ambari has built-in pre-checks that are executed before the
actual upgrade to check the overall health of your cluster and validate its readiness for upgrade. Let us look at the pre-checks, their purpose and how to
remediate the issues, so that your cluster upgrade process is smooth. A bit of background first: Background Ambari supports two kinds of stack (cluster) upgrades: Rolling
Upgrade (RU) and Express Upgrade (EU). Pre-checks apply to both upgrade
methods, although RU has a larger set of pre-checks since the upgrade does not
involve any downtime First up, the types of pre-checks:
Cluster level checks: Example – newer version
packages should be installed on all hosts in the cluster Service level checks: Example – all service
components should be in installed state (no failures) Host level checks: All hosts must be
communicating with Ambari (no network issues, no heartbeat failures from Ambari
agent to server) The output of a pre-check would result in three possible
values of pre-check status:
ERROR WARNING PASS ERRORS that have to be fixed before the upgrade
can be started. WARNINGS are recommended to be fixed, but may be ignored, if
you know what you are doing When you hit ‘Upgrade’ button in Ambari User Interface (UI) – the pre-checks
are kicked off in the background and within a matter of seconds you would be
notified if there are some issues that need to be fixed before upgrade (RU or
EU) can be started. Here is a snippet from Pre-Checks Window in Ambari UI: Behind the scenes, below API call is triggered: curl -u $user:$password -i -H 'X-Requested-By: ambari' -X GET http://$server:8080/api/v1/clusters/$name/rolling_upgrades_check?fields=*&UpgradeChecks/repository_version=$version&UpgradeChecks/upgrade_type=ROLLING
- $user: Ambari admin
user - $password: Password
of the Ambari admin user account - $server: Ambari
server hostname or IP address - $name: Cluster name - $version: The actual
stack version you wish to upgrade to; example: 2.5.0.0-1245 (this must be
registered beforehand and package installation should be completed) - upgrade_type: ROLLING
for Rolling Upgrade, NON_ROLLING for Express Upgrade
============================================================================ Details about the
pre-checks and remediation
Refer ru-eu-prechecks-details.pdf Table above is updated as of Ambari 2.4 release
... View more
Labels:
09-01-2016
06:24 AM
@Ramakrishna Pratapa - Can you attach ambari-server-check-database.log file present in /var/log/ambari-server/ directory? Also please try running: ambari-server start --skip-database-check and let us know how it goes From the first look, the issue appears due to an inconsistency in a service configuration. Additionally, please paste the output of: ambari-server --version -Vivek
... View more
08-26-2016
07:02 PM
2 Kudos
@Saifullah Sajjad - While we await your error log, you just have to place ambari.repo on ambari server node. hdp.repo is not required on any of the nodes as Ambari server takes care of pushing the repos on all nodes that you designate as part of the cluster.
... View more
08-10-2016
06:16 PM
2 Kudos
@Zach Kirsch Check this article from @Kuldeep Kulkarni which has a bunch of scripts that would suit your requirement https://community.hortonworks.com/articles/34747/ambari-admin-utility.html ./ambari-admin.sh restart refresh is the one The source code of the above script as mentioned in the article is available at: https://github.com/crazyadmins/useful-scripts/blob/master/ambari/ambari-admin.sh -Vivek
... View more
08-09-2016
12:59 PM
1 Kudo
@Narasimha Gunturu - In such cases, it is good to write a script to upgrade the agents across all nodes For example: key="/tmp/ambari-keypair"
for i in {1..5} ; do ssh -i $key -o StrictHostKeyChecking=no root@host-$i.mydomain ambari-agent stop ; done
repourl="http://public-repo-1.hortonworks.com/ambari/centos6/2.x/updates/2.2.2.0/ambari.repo"
for i in {1..5} ; do ssh -i $key root@host-$i.mydomain wget -nv $repourl -O /etc/yum.repos.d/ambari.repo; done
for i in {1..5} ; do ssh -i $key root@host-$i.mydomain yum upgrade -y ambari-agent ; done
for i in {1..5} ; do ssh -i $key root@host-$i.mydomain ambari-agent start ; done
Here host-1.mydomain to host-5.mydomain are the five agent nodes and 'key' variable holds the ssh key to connect to those nodes from a central server (could be the Ambari server host)
... View more
08-09-2016
11:09 AM
2 Kudos
@Narasimha Gunturu You would need to upgrade the Ambari agent in other nodes as well. Check below link for details (point #7): http://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_upgrading_Ambari/content/_upgrade_ambari.html Once agents are upgraded and started, they would sync up with Ambari server. All agents should be at same version as Ambari server -Vivek
... View more
08-03-2016
02:34 PM
@Matthias Rueling Can you paste the screenshot of Javascript console window when you click on "Perform Upgrade"? This can be enabled in Chrome browser - View - Developer - Developer Tools - Network tab. It would show the API call (generally the upgrade pre-check call, I think) that is getting invoked and errors if any, depending on its return code The other entries to check would be in /var/log/ambari-server/ambari-server.log on Ambari host. Based on the above two, we can understand the issue and then decide next action -Vivek
... View more
- « Previous
-
- 1
- 2
- Next »