@Sami Ahmad @Divakar Annapureddy if you are using older version of Ambari then you following above mentioned useful links is the best course of action. Ambari-2.4.0 version has added a new feature for being able to delete service from Ambari UI. If you are using Ambari-2.4.0 or higher, you can use Ambari UI to delete a service. The action of deleting a service is available under Service Actions delete-service.png This is more reliable way of deleting a service if using Ambari-2.4.0 (it's the version when feature was addd in the ui) as ui also additionally changes the configs of the cluster when a service is deleted. For example when deleting a Ranger service, ui will automatically turn off Ranger plugins for all services (done by config changes in respective services) and do any other config change required and then delete Ranger service. Also this is now more tested way of deleting service. Basically guaranteed way of other services will still remain healthy and not be affected by deleting any partiuclar service. ... View more

@Jay SenSharma Although above mentioned steps can be more simplified (no need to create other user), they should do the needed work to get user unblock from this issue ... View more

@Sagar Shimpi This seems to be correct approach but few things to be aware of This will resolve issue for the current logged in user but other users will have same issue of seeing "Add service wizard" in progress label unless the current logged in user logs off and logs in back at which user will be directed to add service wizard and then cancels add service wizard. After that this issue will go away for all other ambari users As said above after the execution of the API if current user signs out and signs back in then user will be directly redirected to add service wizard ... View more

@chennuri gouri shankar Expected Ambari Behavior: If any admin user is in the middle of the wizard then other users who signs in should be informed about that. Since all wizard does some specific operations like add/delete components or start/stop service that need to happen in sequence, other logged in user are at that time not allowed to perform any service related operations. This behavior was added after getting feedback from ambari user community as part of https://issues.apache.org/jira/browse/AMBARI-13123. Due to some reason if any admin initiated a wizard but did not complete it or for any unknown bug in ambari, if the label keeps on showing then you can use following steps to make it disappear Go to ambari-web experimental page and reset ui state. Its url is http://c6402.ambari.apache.org:8080/#/experimental. c6402.ambari.apache.org is the ambari-server hostname. I have attached snapshots of the page as well. experimental-page-click-on-reset-ui-state.png Sign out from ambari-web Execute following API call from bash command line with admin privileged user credentials curl -u admin:admin -i -H 'X-Requested-By: ambari' -X POST -d '{"wizard-data":"null"}' http://c6402.ambari.apache.org:8080/api/v1/persist Here admin:admin is username:password and c6402.ambari.apache.org is the ambari-server hostname This will completely resolve the issue. After executing these steps, none of the user login will see any wizard being in progress. Note: when doing this you need to be careful that you are not stepping on any other admin who is in the middle of the wizard. These steps essentially clears all wizard related cached information and the ongoing wizard if any will be hampered If you want to check on the wizard state which ambari thinks is ongoing (add service in your case), then just execute 2nd and 3rd steps mentioned above. Logging in back will take you to the wizard page which was left unfinished before. you can choose to complete or exit from wizard thereafter and then the cache will be automatically cleared and you will no longer see the "ongoing wizard" label on the dashboard page. FYI: I have created https://issues.apache.org/jira/browse/AMBARI-19276 so that going forward only clicking on reset ui button will be sufficient to workaround if user gets stuck in this state. ... View more

@Zack Riesland you can use Ambari's RESTFul APIs to know this on a deployed cluster. For determining ambari server DB use following API: http://c6401.ambari.apache.org:8080/api/v1/services/AMBARI/components/AMBARI_SERVER?fields=RootServiceComponents/properties/server.jdbc.database For determining Hive Metastore DB use following API and lookup for hive_database property http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/configurations/service_config_versions?service_name=HIVE&is_current=true For determining Hive Metastore DB use following API and lookup for oozie_database property http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/configurations/service_config_versions?service_name=OOZIE&is_current=true ... View more