Also: $ ls /usr/hdp 2.2.0.0-2041 2.2.4.2-2 2.3.2.0-2950 current Where current is correctly pointing to 2.3.x ... View more

Nope, not upgrading anything. Ambari database stack options: select * from stack; stack_id | stack_name | stack_version ----------+------------+----------------- 1 | HDP | 2.3 2 | HDP | 2.1.GlusterFS 3 | HDP | 2.2 4 | HDP | 2.1 5 | HDP | 2.0 6 | HDP | 2.0.6 7 | HDP | 2.3.GlusterFS 8 | HDP | 2.0.6.GlusterFS ... View more

Thank you Artem. My current status is up in response to Neeraj's comments. ... View more

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. ... View more

Thanks Neeraj, look forward to connecting. ... View more

I'm in the Northeast. Thank you for the tips. ... View more

Thanks I will keep that in mind as I progress. Support is not very helpful at the moment..that's why dropped by. ... View more

Ah, ok. So execute before starting cluster services to get what's there, execute again after starting services and basically do a diff between the 2? This is good. ... View more

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. ... View more