Member since
06-20-2016
308
Posts
103
Kudos Received
29
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1119 | 09-19-2018 06:31 PM | |
863 | 09-13-2018 09:33 PM | |
744 | 09-04-2018 05:29 PM | |
2258 | 08-27-2018 04:33 PM | |
1921 | 08-22-2018 07:46 PM |
05-21-2019
09:49 PM
1. Get the output from Ambari server http://AMBARI-HOST:8080/api/v1/stacks/HDP/versions?fields=repository_versions/operating_systems/repositories/*,repository_versions/operating_systems/OperatingSystems/*&repository_versions/RepositoryVersions/repository_version=3.1.0.0-78 2. Copy the json of "operating_systems" outer block of step1 output and create repo.json file - it would looks like repo.json 3. update repo.json file to reflect your changes/modifications. 4. now run below API call to update. curl -insecure -H "X-Requested-By:ambari" --user admin:admin --data @repo.json -X PUT http://AMBARI-HOST:8080/api/v1/stacks/HDP/versions/3.1/repository_versions/1 Note: please make sure you include correct repo version id at the end. in this case it is 1 5. Now go and check in UI to see if those changes reflects. Note: This tried and tested in Ambari2.7.x
... View more
- Find more articles tagged with:
- ambari-server
- Cloud & Operations
- How-ToTutorial
- repository
- rest-api
Labels:
11-14-2018
06:33 PM
3 Kudos
Steps to fix below Database consistency WARNINGs in Ambari 2.7.x WARN - You have config(s): webhcat-site-version1540591929056,webhcat-log4j-version1540591928580,hive-exec-log4j-version1540591929168,webhcat-env-version1540591929289,hive-log4j-version1540591929465,hcat-env-version1540591928892 that is(are) not mapped (in serviceconfigmapping table) to any service! CREATE TEMPORARY TABLE orphaned_configs AS
(select config_id,type_name,version_tag from clusterconfig where unmapped != 1 and type_name not in ('cluster-env') and config_id not in (
SELECT
cc.config_id
FROM clusterconfig cc, serviceconfig sc, serviceconfigmapping scm
WHERE cc.type_name != 'cluster-env'
AND cc.config_id = scm.config_id
AND scm.service_config_id = sc.service_config_id));
Update clusterconfig set unmapped = 1 where config_id in (select config_id from orphaned_configs);
drop table orphaned_configs;
If it is 2.6.x then following query can be used SELECT cc.config_id, cc.type_name, cc.version_tag
FROM ambari.clusterconfig cc, ambari.clusterconfig ccm
WHERE cc.config_id NOT IN (SELECT scm.config_id FROM ambari.serviceconfigmapping scm)
AND cc.type_name != 'cluster-env' AND cc.type_name = ccm.type_name AND cc.version_tag =
ccm.version_tag;
CREATE TEMPORARY TABLE orphaned_configs AS
(SELECT cc.config_id FROM ambari.clusterconfig cc WHERE cc.config_id NOT IN
(SELECT scm.config_id FROM ambari.serviceconfigmapping scm) AND cc.type_name !=
'cluster-env');
DELETE FROM ambari.clusterconfig WHERE config_id IN
(SELECT config_id from orphaned_configs);
... View more
- Find more articles tagged with:
- Ambari
- ambari-2.7
- ambari-server
- How-ToTutorial
- Sandbox & Learning
Labels:
10-04-2018
04:47 PM
@Greenhorn Techie Is it failing at the same component? if it is another component then remove all the existing installed components that installed manually ( or outside of Ambari)
... View more
10-02-2018
08:02 PM
@Greenhorn Techie Can you please check if the component is already installed? you can check with yum list installed | grep -i zookeeper-server If it is already installed using some other tag or so - please remove/uninstall so that Ambari can install using the correct repoId tag.
... View more
10-01-2018
05:03 PM
@subramanyam sibbala Can you check your ambari-agent log and see what error it is throwing?
... View more
10-01-2018
04:29 PM
@Greenhorn Techie In VDF file provide the satelite repo tag in "<repoid>TAGNAME</repoid>" and re-create the version and then attempt the installation process.
... View more
09-24-2018
07:46 PM
1 Kudo
@Adnan
Chowdhury
Can you refresh the page and try again? right click and see if there is any Javascript errors?
... View more
09-24-2018
04:25 PM
please open separate thread since this is already closed.
... View more
09-20-2018
04:20 PM
@sandeep gupta please mark the correct answer if it has resolved the issue
... View more
09-20-2018
04:19 PM
@Shraddha Singh Can you first check if those hosts were heart beating to ambari server? You can go http://ambari-server-host:8080/api/v1/hosts and see if it shows any hosts. If it is not showing then go to ambari agents and check if there is any errors at /var/log/ambari-agent/ambari-agent.log
... View more
09-19-2018
06:31 PM
@sandeep gupta Do you have any hosts are not heart beating in the cluster? or any nodes are in "Maintenance Mode" ? Basically Ambari server does the host check call for all the hosts ( I guess all master component hosts) and if any one of them down then it keep showing that screen. so make sure all hosts are heart beating and then not in MM. One of the workaround is to disable the Hostcheck call and attempt to add again. Login to Ambari in one tab and in another tag open "http://AMBARI-HOST:8080/#/experimental" and select "disableHostCheckOnAddHostWizard" checkbox and save it. Now you can attempt to add the node again.
... View more
09-18-2018
10:13 PM
If cluster is installed with Ambari 2.5 , Upgrading to Ambari2.6.x cause service re-start ( client) failure and Add service also fails with installation. with above combination, you might be hitting https://issues.apache.org/jira/browse/AMBARI-24629 if you see error like below 2018-09-15 08:37:13,748 - Looking for matching packages in the following repositories: HDP-2.6, HDP-UTILS-1.1.0.21 2018-09-15
08:37:15,841 - No package found for hive_${stack_version}(hive_(\d|_)+$) 2018-09-15
08:37:15,844 - The repository with version 2.6.1.0-129 for this command has been marked as resolved. It will be used to report the version of the component which was installed root cause is already explained in the BUG. How to fix the issue: 1. First find out what is your current version repo version id. in browser go to http://apappu3.hdp.com:8080/api/v1/stacks/HDP/versions/2.6/repository_versions?fields=operating_systems/repositories/Repositories/base_url From the response find out the repository_version_id for the version. 2. Now create /tmp/data.json with below content {
"operating_systems" : [
{
"OperatingSystems" : {
"ambari_managed_repositories": false,
"os_type" : "redhat6",
"stack_name" : "HDP",
"stack_version" : "2.6"
},
"repositories" : [
{
"Repositories" : {
"base_url" : "",
"repo_id" : "MY-ID",
"repo_name" : "MY_name"
}
},
{
"Repositories" : {
"base_url" : "",
"repo_id" : "MY-UTILS",
"repo_name" : "MY-UTILS_name"
}
}
]
}
]
}
Note: replace "MY-ID"/"MY-UTILS" with the actual sateliterepotag and os_type as well. 3. now run below curl call to update it. curl -u admin -H "X-Requested-By: ambari" --data @data.json -X PUT /api/v1/stacks/HDP/versions/2.6/repository_versions/ID Now - refresh the UI and see if the updated tags are visible in version definition. Note: Please take Ambari database backup before running the CURL call
... View more
- Find more articles tagged with:
- Ambari
- ambari-server
- Cloud & Operations
- FAQ
Labels:
09-18-2018
09:51 PM
Many times Ambari throws installation errors like "No package found for hive_${stack_version}(hive_(\d|_)+$) ..." There can be many reasons for this failure. The root cause for this issue is, basically Ambari could not be able to determine the installable package. Reason1: Check if the same package is already installed using different repoid/sateliterepotag. that can be check using below command yum list installed | grep packagename
Ex: yum list installed | grep hive If it shows the entries then determine if those are installed with different repoid/sateliterepotag. In Ambari task logs you can find what tag/repo Ambari is using to install Now see "yum list installed" has the correct repoId - if it is not matching then manually uninstall that library and let Ambari install it. Reason2: If you are using Satelite repository - Ambari should show the repo tag name at "Applicable repositories: Satelitehdp265.." If it is not showing correctly, that means you repo version definition is incorrect. Make sure sateliterepo tag is defined correctly. Reason3: If you have installed the cluster with Ambari 2.5.x and then upgraded to Ambari2.6.x then you might encounter AMBARI-24629 bug. please follow https://community.hortonworks.com/articles/223111/service-restartadd-fails-after-upgrading-to-ambari.html to fix that issue.
... View more
- Find more articles tagged with:
- Ambari
- ambari-server
- Cloud & Operations
- How-ToTutorial
Labels:
09-14-2018
08:36 PM
Please attach a screenshot. also see if there is any errors in ambari-server.log file
... View more
09-14-2018
08:28 PM
@joel patterson, What error are you getting at 99% stage?
... View more
09-13-2018
11:26 PM
When Ambari executes tasks like START/STOP/RESTART/... , it timeouts after waiting 20mins ( 1200 seconds). For example Namenode START command waits for 20mins and then mark the service is Failed/Timeout - in larger clusters NameNodes takes much longer time - How to tell Ambari to wait for much longer? Add below 2 configs and re-start the service - this change increases the timeout value to 1Hour. agent.task.timeout=3600
server.task.timeout=3600
Note: This change may not take affect during the Upgrade If it is already scheduled.
... View more
- Find more articles tagged with:
- ambari-server
- How-ToTutorial
- operations
- Sandbox & Learning
Labels:
09-13-2018
10:35 PM
While Upgrading/Downgrading HDP in Ambari, if you see "Unable to determine the stack and stack version" it is possible the repo version has some inconsistency. Post Ambari2.6.x, should have repo_version table "resolved" column as 1 - If it shows "0" then run below update query. update repo_version set resolved = 1 Re-start Ambari and then attempt the operation again - it should go through. Note: As of now it is not a BUG as we could not able to reproduce the issue.
... View more
- Find more articles tagged with:
- ambari-server
- Cloud & Operations
- How-ToTutorial
- upgrade
Labels:
09-13-2018
09:33 PM
@Jorge Luis Hernandez Olmos If you are using Ambari - you can find that from task logs in the UI.
... View more
09-10-2018
04:53 PM
@suresh kumar please check ambari-server.log for more details on that. and then check actual error at /var/run/ambari-server/stack-recommendations/XXX/
... View more
09-04-2018
06:24 PM
@Michael Bronson What kind of corruption is that? file is incomplete or less size that it should be?
... View more
09-04-2018
05:29 PM
@Manoj Nirale In Ambari there is nothing like setting connection timeout for 10hours. You mean to say services should not impact when hosts come back? You can use Auto-start feature in Ambari at https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.1.5/bk_ambari-operations/content/enable_service_auto_start.html With this as soon as hosts starts - Ambari would try and start those services. Let me know if you have any more questions on this.
... View more
09-04-2018
05:23 PM
@Alaa
Nabil
what error do you see in nodemanager logs? please post the error/log snippet here to understand that root cause.
... View more
09-04-2018
05:19 PM
1 Kudo
@Takefumi Oide You can follow the article given at https://community.hortonworks.com/content/supportkb/151074/how-to-perform-hdfs-metadata-backup-and-faqs.html Ambari does not provide any option for backup in this case.
... View more
09-04-2018
05:09 PM
@Bharadwaj Bhimavarapu You cluster in Database has the "AMBARI_INFRA" service added but for some reason your stack does not have the service definition at the file system /var/lib/ambari-server/resources/common-services/ and /var/lib/ambari-server/resources/stacks/HDF/3.1/services If you are not using that service then you can clean up from the database using below article and then attempt the Upgrade. https://community.hortonworks.com/articles/79546/how-to-cleanup-service-from-ambari-database.html
... View more
08-31-2018
09:44 PM
@Veerendra Nath Jasthi Did you apply 3.1.2 mpack before attempting 3rd step?
... View more
08-31-2018
05:54 PM
@Veerendra Nath Jasthi If you have Ambari Database backup then restore it first - then attempt to upgrade again and see if that helps. please take current DB backup as well in case of any issues.
... View more
08-31-2018
05:29 PM
@Veerendra Nath Jasthi Did you follow correct order while upgrading? As per this document https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.1.2/bk_ambari-upgrade/content/preparing_to_upgrade_ambari.html 1. First Ambari binary upgrade ( yum upgrade ambari-server) 2. apply mpack 3. Ambari DB upgrade.( ambari-server upgrade)
... View more
08-31-2018
04:17 PM
@Veerendra Nath Jasthi Can you tell at which operation are you seeing that error? also provide full trace of the error.
... View more
08-29-2018
10:40 PM
In Ambari when try to upgrade to HDP/HDF versions - after adding a new repo version, some times it might show disabled "install packages" button. There can be multiple reasons for this. 1. Check to stack_id which stack_id clusters table is pointing to. it should be pointed to correct current stack_id if not correct with update query 2. check clusterstate table - it should be pointing to correct current stack_id if not correct with update query 3. How to find my correct current stack_id run "select stack_id, version from repo_version" query - check the stack_id for your current hdp/hdf version. 4. so step1 and step2 should be pointing to stack_id returned in step3. There can be many other reasons like not having "upgrades" folder in stack folder or some other.
... View more
- Find more articles tagged with:
- Ambari
- ambari-server
- Cloud & Operations
- FAQ
- hdf-upgrade
- hdp-upgrade
- upgrade
Labels: