Hi Marc, I understand your frustration with the project, but I think a few points need to be clarified, and some expectations need to be realigned.
First, the BIGTOP stack in Ambari follows a *stack inheritance model*, as described here: https://ambari.apache.org/docs/2.7.8/ambari-design/stack-and-services/stack-inheritance Because of this, *not every service or file must be redefined or duplicated in each stack version*. A stack such as 3.3.0 can legitimately reference artifacts inherited from 3.2.0 or earlier, even if a service was introduced or fully enabled later. This is expected behavior and not, by itself, an error or ambiguity. Second, Ambari is a mature and stable project, but like any complex open-source software, it still has areas that can and should be improved. Those improvements, however, happen through *constructive collaboration*. Raising concerns is welcome, but doing so without proposing solutions, patches, or even concrete suggestions does not move the project forward. Statements questioning the credibility of the software or the community, without engaging in the contribution process (JIRAs, patches, reviews, or design discussions), do not help resolve the issues you are experiencing. If you believe there is a real inconsistency or bug, the best path forward is to: - Open a JIRA with a clear technical description - Propose a fix or at least a concrete improvement - Engage with the community to validate the approach The community only benefits when its members are willing to collaborate, share knowledge, and contribute — not just point out problems. Best regards, Jefferson Almeida Em ter., 13 de jan. de 2026 às 05:09, Marc Hoppins <[email protected]> escreveu: > Hi, Brendan/All, > > > > *ambari-server/src/main/resources/stacks/3.3.0/RANGER/alerts.json* > references > *BIGTOP/3.2.0/services/RANGER/package/alerts/alert_ranger_admin_passwd_check.py* > > > > How is this ever going to work if 3.2.0 does not even have ranger ? > > > > 3.2.0/properties/stack_packages.json makes declarations for ranger-admin, > ranger-tagsync and ranger-usersync but, again, RANGER does not appear to be > a part of 3.2.0 > > > > Is this why I still see errors regarding 3.2.0 when I suggest I want 3.3.0? > > > > I am still mystified by this software which has such useful potential but > so much incredible ambiguity. > > > > For the developers: WHY was a simple correction and rebuilt collection > made available as soon as the typo was discovered? No mention in the > official pages ANYWHERE that this problem exists, and that the prebuilt > (downloadable) binaries will not operate as required. > > > > Marc > > > > *From:* Brenden Cobb <[email protected]> > *Sent:* Friday, December 5, 2025 11:00 PM > *To:* [email protected] > *Subject:* Re: [EXT]Re: Help needed > > > > [External Sender] > > Hi Marc - Sorry for the delay… What happens when you run yum install > hadoop_3_3_0 via CLI? > > Your response suggests you were trying to install “Hadoop_3_0_0” > > > > > > I would suggest double-checking building Ambari: > > https://ambari.apache.org/docs/3.0.0/ambari-dev/building-from-source > > > > And building Bigtop for Ambari: > > https://ambari.apache.org/docs/3.0.0/ambari-dev/bigtop-guide > > > > I also found the info here useful for building: > > > https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0 > > > > > > The “component did not advertise a version” message suggests something > amiss on of the builds. > > > > > > The stacks are specified here: > https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/BIGTOP > > > > > > I’m not a Ambari contributor, so I can only help so much based on my > personal experience building ambari/bigtop and running on Rocky 8. > > > > > > Cheers > > > > > > > > > > > > *From: *Marc Hoppins <[email protected]> > *Date: *Thursday, November 27, 2025 at 5:57 AM > *To: *[email protected] <[email protected]> > *Subject: *RE: [EXT]Re: Help needed > > Hi, Brendan, > > Sorry for the delay. I decided to wipe the slate clean and begin from the > start. > > > > So, now I am thinking the important part is the actual source. > > > > I followed your link and downloaded the ZIP. I corrected the tagsync typo > and rebuilt. No problems. I installed, created a test cluster and > re-installed to targets. > > > > > > So I tried installing on one target via commandline: yum install -y > Hadoop_3_0_0 > > > > Lo, and behold, success. So, I am of the opinion that 3.2.0 is hardcoded > into the source somewhere. Surely this would make any attempt to upgrade a > complete failure? > > > > Where am I looking to fix in the source? > > > > Marc > > > > *From:* Brenden Cobb <[email protected]> > *Sent:* Thursday, November 20, 2025 10:25 PM > *To:* [email protected] > *Subject:* Re: [EXT]Re: Help needed > > > > [External Sender] > > I’m not sure why BIGTOP 3.2.0 is referenced in the output, but it is > trying to install the Bigtop 3.3.0 package for Hadoop client. Is the repo > available? What happens when you try to execute the yum install command > that is producing the error? > > > > *From: *Marc Hoppins <*[email protected] > <[email protected]>*> > *Date: *Thursday, November 20, 2025 at 3:49 AM > *To: **[email protected] <[email protected]>* > <*[email protected] > <[email protected]>*> > *Subject: *RE: [EXT]Re: Help needed > > Well, after doing all those steps… > > > > > > *From:* Brenden Cobb <*[email protected] > <[email protected]>*> > *Sent:* Wednesday, November 19, 2025 9:03 PM > *To:* *[email protected] <[email protected]>* > *Subject:* Re: [EXT]Re: Help needed > > > > [External Sender] > > Seems like there may be some artifacts from previous installation > > > > These are steps I have used before to clean up, prior to re-installing: > > *https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114 > <https://community.cloudera.com/t5/Support-Questions/How-to-Completely-Clean-Remove-or-Uninstall-Ambari-for-Fresh/m-p/95114>* > > > > > > > > *From: *Marc Hoppins <*[email protected] > <[email protected]>*> > *Date: *Wednesday, November 19, 2025 at 9:15 AM > *To: **[email protected] <[email protected]>* > <*[email protected] > <[email protected]>*>, *[email protected] > <[email protected]>* <*[email protected] <[email protected]>*> > *Subject: *RE: [EXT]Re: Help needed > > Hi, Brendan, > > > > I appreciate the information. I downloaded and rebuilt 3.0.0. > > > > First, ambari-server changed from a HASH=”hexnumber” to > HASH=”${buildnumber}” which fails the server start. > > > > Second, am STILL seeing 3.2.0 when I clearly selected 3.3.0 and this is > failing host installs. Where am I likely to find this problem because > selecting in the ambari UI is not making the right choice. I dumped the > ambari database and started afresh but no joy. > > > > > > *From:* Brenden Cobb <*[email protected] > <[email protected]>*> > *Sent:* Tuesday, November 18, 2025 8:05 PM > *To:* *[email protected] <[email protected]>*; > *[email protected] > <[email protected]>* > *Subject:* [EXT]Re: Help needed > > > > [External Sender] > > Hi - > > > > The latest release of Ambari is version 3.0.0. Running a later build is > likely to surface errors. > > > > To try and fix the Ranger issue from your previous email, I would suggest > building Ambari version 3.0.0 > *https://github.com/apache/ambari/tree/release-3.0.0 > <https://github.com/apache/ambari/tree/release-3.0.0>*, patched with the > change in: *https://issues.apache.org/jira/browse/AMBARI-26427 > <https://issues.apache.org/jira/browse/AMBARI-26427>* > > > > *From: *Marc Hoppins <*[email protected] > <[email protected]>*> > *Date: *Tuesday, November 18, 2025 at 8:01 AM > *To: **[email protected] <[email protected]>* > <*[email protected] > <[email protected]>*>, *[email protected] > <[email protected]>* <*[email protected] <[email protected]>*> > *Subject: *Help needed > > Hi, All…Anyone, > > > > I downloaded and tried 3.0.0 but got the ranger error regarding > translations. So I downloaded 3.1.0 and run a build. I am NOT very familiar > with all of eclipse but assume I got things right as I saw no errors. > > > > I installed 3.1.0 and purged any packages on my target nodes. I then > installed the ambari-agent on targets to 3.1.0. > > > > I started with a clean ambari database. > > > > I did not download and build either metrics or infra but stuck with the > existing rpms from the 3.0.0 install. > > > > I was a bit concerned with the ‘build from source’ instructions as it is > suggesting BIGTOP-3.2.0 which appears to be going backwards. Especially as > 3.2.0 is Centos8 and I am attempting to use Rocky Linux 9. > > > > Running the ambari server now, I see cluster install options for BIGTOP > 3.4.0, 3.3.0, 3.2.0. As I had followed the 3.3.0 install I had my > repository setup with 3.3.0 and was expecting I could use that. > > > > Warnings and errors abound and when I checked the running process I saw a > running agent process > > > > /usr/bin/python3 > /var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package…. > > > > If I had selected 3.3.0 why am I seeing 3.2.0? If it is not possible to > use 3.3.0 or 3.4.0 why are they included? > > > > Any information would be appreciated. > > > > Marc >
