I had to restore an Ambari database backup, which was a bit behind the current cluster status. Will the Ambari restore "rollback" config changes upon cluster startup, and if so is there a way to "refresh" Ambari with what's current in the cluster. Thank you.
Thank you both for your help. Support case was escalated and received excellent guidance for getting Ambari back in sync. The primary resolution for the sync issue raised here was executing $ ambari-server upgradestack HDP-2.3
Thanks. For 1) This sounds like Ambari will overwrite existing component configs when using a database restore? For 2) is the blueprint created from Ambari's settings or the cluster's configs? I'm just not clear whether Ambari will overwrite what's in the cluster or pull, and if there's an option to control this behavior.
As suggested, I have the blueprint which reflects all the current information for our stack (2.3.2). When attempting to start services on the cluster Ambari favors 2.2, the previously installed version. My assumption is the Ambari database needs some adjusting to properly recognize 2.3.2. I've tried a few updates to set the installed stack to 2.3.2, but Ambari is unsuccessful at starting the cluster components.
since this is after-effect, I'd open a ticket with support. In my experience, i would backup all configs on every node, then try to restart agent on one node at a time as agent will advertise current config on a node to ambari server. Once you confirm everything is restored for that node, you can go to next node.
@Brenden Cobb no problem, I escalated your issue to get proper attention. I'm in Northeast, if you have similar issues, you can reach out to me directly. Also, please post your current status as this thread also needs to know the solution :).