Hi all. I'm new here.
So at work we provide a service that's been running flawlessly on top of HDP since at least 2014. The recent "events" (which we became aware of only late last year, when it was already too late) had us panicking a bit at first, since we realised we could no longer manage our cluster, but we've since then been able to track down repo mirrors so the immediate crisis is over (no thanks to Cloudera). However, with HDP dead and CentOS 7 nearing EOL, it's clear that we need to move on. While we have evaluated both CDP, GCP Dataproc and even considered migrating from HBase to Bigtable, Bigtop seems like the only sensible way forward. We just want a small database/MQ backend cluster that keeps running forever to power our service. Which brings us to Ambari. I really liked Ambari, for cluster management obviously but also so for monitoring, and it has worked great for us all those years. A lot of work has obviously been put into Ambari and it seems like such a waste to throw it all away. What are this Bigtop's plans for Ambari, the upstream project being retired and all? For us, we would like to bring us to the point were, in 2024 when CentOS 7 goes EOL, we can bring up a new cluster on Rocky 8 with HDFS, Yarn, HBase, Kafka and Zookeeper using Ambari to manage, monitor and keep it up and running like that until at least 2029 when RL8 retires. It doesn't seem *that* difficult given the HDP 3.1 vs Bigtop 3.0.1 BOMs for the components we need. We would also be willing to put some time into making that happening. What are your thoughts on that? Is anybody here still interested in Ambari? Has anybody actually been using it to manage Bigtop components? PS. Also cross-posting to user. Anybody else in my situation? What are you all using to monitor your clusters once deployed? -- Martin Blom [email protected]
