Re: Issues building ambari v2.7.3 "on project ambari-metrics-storm-sink-legacy"

[Reed Villanueva]

I was not cloning via git (should I be, if so which branch is recommended)?
The installation docs I was following did not mention optionally using the
git repo fro installation, so I assumed it was not the recommended way (eg.
the code from the apache archive or mirror would be the most stable).
I am simply following the installation docs here:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.3

 And downloading the .tar.gz from:
https://archive.apache.org/dist/ambari/ambari-2.7.3/

On Sun, Nov 3, 2019 at 4:58 PM Akhil Naik  wrote:

> Hi Reed,
>
> Not Sure which branch you are trying to build.
> If it's branch-2.7 there was a Apache JIRA filed :
> https://issues.apache.org/jira/browse/AMBARI-25348
> after which the pom.xml was changed 
> https://nexus-private.hortonworks.com/nexus/
> to https://repo.hortonworks.com/
>
> refer to : https://github.com/apache/ambari/pull/3063/files
>
> and change your pom.xml accordingly.
>
>
>
>
> *Thanks,Akhil Subhash Naik*
>
> --
>
>
> On Sat, Nov 2, 2019 at 1:26 AM Reed Villanueva 
> wrote:
>
>> After waiting for project to build found that problem not fixed.
>> When using the nexus-hortonworks mirror, it appears that maven is also
>> looking there for an artifact called "ring-cors" and failing (I assume due
>> to the fact that I have it configured as a mirrorOf *). Moving the mirror
>> info to the project pom.xml, I get the same error again:
>>
>> [ERROR] Failed to execute goal on project
>> ambari-metrics-storm-sink-legacy: Could not resolve dependencies for
>> project org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.3.0.0:
>> Failed to collect dependencies at
>> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557: Failed to read
>> artifact descriptor for
>> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557: Could not transfer
>> artifact org.apache.storm:storm-core:pom:0.10.0.2.3.0.0-2557 from/to
>> apache-hadoop (
>> http://nexus-private.hortonworks.com/nexus/content/groups/public):
>> Connect to nexus-private.hortonworks.com:80 [
>> nexus-private.hortonworks.com/54.173.242.72] failed: Connection timed
>> out (Connection timed out) -> [Help 1]
>>
>> Anyone with more maven experience know how to fix this issue? Anyone else
>> had this issue building the project?
>>
>>
>> On Thu, Oct 31, 2019 at 12:38 PM Reed Villanueva 
>> wrote:
>>
>>> Fixed issue.
>>> My $M2_HOME/conf/setting.xml now looks like...
>>>
>>> 
>>> 
>>> 
>>> nexus-hortonworks
>>> *,!central
>>> Nexus hortonworks
>>> 
>>> https://repo.hortonworks.com/content/groups/public/
>>> 
>>>   
>>> 
>>>
>>>
>>> On Thu, Oct 31, 2019 at 11:40 AM Reed Villanueva 
>>> wrote:
>>>
 Problem seems similar to the Taiwanese post here:
 https://translate.google.com/translate?hl=en=zh-TW=https://www.twblogs.net/a/5d5f397bbd9eee541c328e0c=search

 Not very experienced with maven, so not totally sure how to interpret
 their steps, but will continue trying to fix and debug.

 On Thu, Oct 31, 2019 at 11:10 AM Reed Villanueva 
 wrote:

> Installed latest version of maven:
> [root@HW001 apache-ambari-2.7.3-src]# mvn --version
> Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117;
> 2019-08-27T05:06:16-10:00)
> Maven home: /usr/local/src/apache-maven
> Java version: 1.8.0_151, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el7_4.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-693.11.1.el7.x86_64", arch:
> "amd64", family: "unix"
>
> Still getting errors:
> [ERROR] Failed to execute goal on project
> ambari-metrics-storm-sink-legacy: Could not resolve dependencies for
> project org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.3.0.0:
> Failed to collect dependencies at
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557: Failed to read
> artifact descriptor for
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557: Could not transfer
> artifact org.apache.storm:storm-core:pom:0.10.0.2.3.0.0-2557 from/to
> apache-hadoop (
> http://nexus-private.hortonworks.com/nexus/content/groups/public):
> Connect to nexus-private.hortonworks.com:80 [
> nexus-private.hortonworks.com/54.173.242.72] failed: Connection timed
> out (Connection timed out) -> [Help 1]
>
> On Thu, Oct 31, 2019 at 10:31 AM Reed Villanueva <
> rvillanu...@ucera.org> wrote:
>
>> UPDATE:
>> New error message:
>> [ERROR] Failed to execute goal
>> com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn
>> (install node and yarn) on project ambari-web: The plugin
>> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 
>> 3.1.0
>> -> [Help 1]
>>
>> Prereq. versions:
>>
>> [root@HW001 

Re: [EXTERNAL]Difference between installing from Apache vs Hortonworks

[Reed Villanueva]

Thanks for the info.
For others, a bit more information from the Cloudera forums can be found
here:
https://community.cloudera.com/t5/Support-Questions/Difference-between-installing-from-Apache-vs-Hortonworks/m-p/281996/highlight/true#M209704

On Mon, Nov 4, 2019 at 8:46 AM Jonathan Hurley  wrote:

> Yes, there is typically a slight difference between the x.y.z version from
> Apache and that offered by Hortonworks. The Hortonworks version usually
> contains several additional fixes that did not make it into the official
> Apache release. Additionally, there are stacks shipped with the Hortonworks
> version which are not shipped with the Apache version.
>
> On Fri, Nov 1, 2019 at 7:13 PM Reed Villanueva 
> wrote:
>
>> I actually meant something more along the lines of: Is the underlying
>> code any different when getting the same ambari version from Hortonworks vs
>> building from source via the apache docs? And the reason for asking was due
>> to the differences in installation method, yet having both marketed as
>> "Apache".
>>
>> And I agree that the package manager is much easier than via the maven
>> build, but that was partly why I was asking if the actual underlying code
>> had any difference.
>>
>> On Fri, Nov 1, 2019 at 10:51 AM Preston, Dale <
>> dale.pres...@conocophillips.com> wrote:
>>
>>> The difference is huge.  From Hortonworks, you can install packages
>>> using your package manager.  Building and deploying from Maven is not a
>>> light undertaking.  I’ve done it a couple times out of obstinance and
>>> stubbornness just to say I had.  I was eventually successful but I wouldn’t
>>> want to do it again.
>>>
>>>
>>>
>>> *From:* Reed Villanueva 
>>> *Sent:* Friday, November 1, 2019 3:03 PM
>>> *To:* user@ambari.apache.org
>>> *Subject:* [EXTERNAL]Difference between installing from Apache vs
>>> Hortonworks
>>>
>>>
>>>
>>> Is there a difference between installing ambari via the apache docs
>>> 
>>> vs Hortonworks docs
>>> 
>>> ?
>>>
>>>
>>>
>>> I assume that the end result is exactly the same since Hortonworks
>>> labels the distribution in the docs as "Apache" and the repo they instruct
>>> to add uses apache.org
>>> 
>>> as the package URL:
>>>
>>> [root@HW001 ~]# yum info ambari-server
>>> Installed Packages
>>> Name: ambari-server
>>> Arch: x86_64
>>> Version : 2.7.3.0
>>> Release : 139
>>> Size: 418 M
>>> Repo: installed
>>> From repo   : ambari-2.7.3.0
>>> Summary : Ambari Server
>>> URL : http://www.apache.org
>>> 
>>> License : (c) Apache Software Foundation
>>> Description : Maven Recipe: RPM Package.
>>>
>>>
>>>
>>> However, the installation instructions that the ambari project site
>>> links to are different and only involve building from source via maven (and
>>> seem to nowhere mention installation options via package manager), so gives
>>> me pause as to whether these are exactly the same.
>>>
>>>
>>>
>>> Could anyone with more experience here explain this a bit more to me?
>>>
>>>
>>> This electronic message is intended only for the named
>>> recipient, and may contain information that is confidential or
>>> privileged. If you are not the intended recipient, you are
>>> hereby notified that any disclosure, copying, distribution or
>>> use of the contents of this message is strictly prohibited. If
>>> you have received this message in error or are not the named
>>> recipient, please notify us immediately by contacting the
>>> sender at the electronic mail address noted above, and delete
>>> and destroy all copies of this message. Thank you.
>>>
>>
>> This electronic message is intended only for the named
>> recipient, and may contain information that is confidential 

Re: [EXTERNAL]Difference between installing from Apache vs Hortonworks

[Jonathan Hurley]

Yes, there is typically a slight difference between the x.y.z version from
Apache and that offered by Hortonworks. The Hortonworks version usually
contains several additional fixes that did not make it into the official
Apache release. Additionally, there are stacks shipped with the Hortonworks
version which are not shipped with the Apache version.

On Fri, Nov 1, 2019 at 7:13 PM Reed Villanueva 
wrote:

> I actually meant something more along the lines of: Is the underlying code
> any different when getting the same ambari version from Hortonworks vs
> building from source via the apache docs? And the reason for asking was due
> to the differences in installation method, yet having both marketed as
> "Apache".
>
> And I agree that the package manager is much easier than via the maven
> build, but that was partly why I was asking if the actual underlying code
> had any difference.
>
> On Fri, Nov 1, 2019 at 10:51 AM Preston, Dale <
> dale.pres...@conocophillips.com> wrote:
>
>> The difference is huge.  From Hortonworks, you can install packages using
>> your package manager.  Building and deploying from Maven is not a light
>> undertaking.  I’ve done it a couple times out of obstinance and
>> stubbornness just to say I had.  I was eventually successful but I wouldn’t
>> want to do it again.
>>
>>
>>
>> *From:* Reed Villanueva 
>> *Sent:* Friday, November 1, 2019 3:03 PM
>> *To:* user@ambari.apache.org
>> *Subject:* [EXTERNAL]Difference between installing from Apache vs
>> Hortonworks
>>
>>
>>
>> Is there a difference between installing ambari via the apache docs
>> 
>> vs Hortonworks docs
>> 
>> ?
>>
>>
>>
>> I assume that the end result is exactly the same since Hortonworks labels
>> the distribution in the docs as "Apache" and the repo they instruct to add
>> uses apache.org
>> 
>> as the package URL:
>>
>> [root@HW001 ~]# yum info ambari-server
>> Installed Packages
>> Name: ambari-server
>> Arch: x86_64
>> Version : 2.7.3.0
>> Release : 139
>> Size: 418 M
>> Repo: installed
>> From repo   : ambari-2.7.3.0
>> Summary : Ambari Server
>> URL : http://www.apache.org
>> 
>> License : (c) Apache Software Foundation
>> Description : Maven Recipe: RPM Package.
>>
>>
>>
>> However, the installation instructions that the ambari project site links
>> to are different and only involve building from source via maven (and seem
>> to nowhere mention installation options via package manager), so gives me
>> pause as to whether these are exactly the same.
>>
>>
>>
>> Could anyone with more experience here explain this a bit more to me?
>>
>>
>> This electronic message is intended only for the named
>> recipient, and may contain information that is confidential or
>> privileged. If you are not the intended recipient, you are
>> hereby notified that any disclosure, copying, distribution or
>> use of the contents of this message is strictly prohibited. If
>> you have received this message in error or are not the named
>> recipient, please notify us immediately by contacting the
>> sender at the electronic mail address noted above, and delete
>> and destroy all copies of this message. Thank you.
>>
>
> This electronic message is intended only for the named
> recipient, and may contain information that is confidential or
> privileged. If you are not the intended recipient, you are
> hereby notified that any disclosure, copying, distribution or
> use of the contents of this message is strictly prohibited. If
> you have received this message in error or are not the named
> recipient, please notify us immediately by contacting the
> sender at the electronic mail address noted above, and delete
> and destroy all