-1 

I ran tests using the dev RC1 build.  I build executables from source and 
installed on a HDP 2.4 system with JAVA 1.7 using our new Ambari plug-in.

The good news is - the source build went fine with no unexpected errors!

However, I was not able to successfully initialize trafodion.  In addition, I 
ran into several issues during testing.
Most of them were minor or my mistakes.  One of them preventing me from 
completing the installation hence a -1.

>>>>>>  Minor - something to fix for the next release.
As part of building Trafodion, the env.sh script is run.  This script reports:

"    If you haven't set HBASE_DISTRO, please set it before source current file
      export HBASE_DISTRO=APACHE1.0 (APACHE HBASE1.0)
      export HBASE_DISTRO=APACHE1.1 (APACHE HBASE1.1)
      export HBASE_DISTRO=CDH5.4    (cloudera 1.0.0-cdh5.4.4) 
      export HBASE_DISTRO=CDH5.5    (cloudera 1.0.0-cdh5.5.1) 
      export HBASE_DISTRO=HDP       (hortonworks 2.3)

   . . . "

The distro number are out of date:
Should create a JIRA to fix this message when env.sh is run.  Probably should 
not include actual distro values in text.

>>>>>> minor - contributors guide update

The https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source section 
of the contributor guide indicates that "make package" is required to build 
binaries.  However, to build the RPM packages for Ambari, you need to do "make 
package-all".  I just did a make package and it did not create all the RPM's 
needed to use the Ambari installer.

>>>>>>  contributors guide

A section should be added to the 
https://cwiki.apache.org/confluence/display/TRAFODION/Create+Test+Environment 
section that talks about using Ambari to install Trafodion.  Suggest that a few 
paragraphs be added that mention the ../distribution directory that contains 
the newly built executables and RPM's and point to the provisioning guide 
http://trafodion.apache.org/docs/provisioning_guide/index.html#install-ambari 
where the Ambari installation is performed.  Just to make a smooth transition 
from build sources to installing in Ambari.

>>>>>> provisioning guide

In section 6 - the following statement is made:

"On your web server host, be sure the createrepo package is installed. Copy the 
two RPM files into a directory served to the web and run the createrepo 
command."

Since I built Trafodion from a source package, I was not sure what the names of 
the two RPM files are and where to pick them up.  The traf_ambari RPM resides 
in the ../distribution directory and the other RPM resides in 
../distribution/RH6 directory.   I ran into a few difficulties since I had 
never created an RPM repository before.  I assume that most installers know how 
to handle this.  Perhaps for us novices, we could add something in the 
contributors guide.

>>>>>> Ambari installation

These issues are related to the Ambari installer and are not necessarily part 
of the Trafodion release package but since they blocked my progress thought I 
would include them here.

- It took me a couple of tries before I got the correct RPMs in trafodion setup 
for Ambari to be acceptable.  Not sure what happened the first time but 
something did not get initialize correctly.  When Ambari tried to install 
trafodion it returned: "Invalid Request: A minimum of one sub-resource must be 
specified for creation."  and the procedure hung.  More investigation seemed to 
indicate that there was a problem with the custom plug-in.  I suspect that I 
did not load my RPM's correctly.

- I installed on a two node cluster that had Kerberos enabled on the system but 
I did not enable Kerberos in Ambari.  However, a couple of security 
co-processors were added which caused issues during Trafodion creation.  I 
incorrectly removed these co-processors.  When this happened, HBase did not 
come up successfully.  But I did not notice that the regionservers were down 
and tried to install Trafodion.  During installation, the process hung.  
Looking at the cluster, an error was returning trying to start TM because it 
could not talk to HBase.  The TM would core dump every couple of minutes and 
retry.  Even though this is not normal, we may want to kill the installation if 
it takes too long.  I know we do check for HBase availability during startup so 
not sure why this check did not kick in.  Maybe because the master was running 
and only the region servers were down.

- After the regionserver issue was resolved, I was able to complete the 
installation and run the initialize metadata step.  According to Ambari, 
everything worked fine.  However, after logging onto the system, trafodion was 
not installed.  When I manually tried to install Trafodion, the following error 
was returned:
 
>>initialize trafodion;

*** ERROR[2034] $Z000PB6:85: Operating system error 201 while communicating 
with server process $Z000R4P:90.

*** ERROR[8904] SQL did not receive a reply from MXUDR, possibly caused by 
internal errors when executing user-defined routines.

*** ERROR[1231] User-defined routine TRAFODION."_LIBMGR_".ADDLIB could not be 
created.

After debugging this, there seems to be a versioning error with the T2 driver . 
 This is a showstopper. 

>>>>> suggestion, as part of initialize step of Ambari installation process, 
>>>>> perhaps an error should be reported if error occurred during the process.

  Roberta

-----Original Message-----
From: Sandhya Sundaresan [mailto:[email protected]] 
Sent: Friday, March 24, 2017 2:01 PM
To: [email protected]
Subject: RE: [VOTE] Apache Trafodion release 2.1.0 ready for release - release 
candidate 1

Thanks for the feedback Steve.
We can fix these in RC2. 
Still waiting for a few more people to try the artifacts out  and send back 
their feedback in case there is more to fix before RC2. 

Thanks
Sandhya

-----Original Message-----
From: Steve Varnau [mailto:[email protected]] 
Sent: Thursday, March 23, 2017 9:15 PM
To: [email protected]
Subject: RE: [VOTE] Apache Trafodion release 2.1.0 ready for release - release 
candidate 1

Nice job putting release together. I found 3 things that may be issues.

-1 (binding)

Potential issues:
* I think the key signature should reference your apache.org address, not a 
corporate email.
* NOTICE file does not have 2017 in the copyright.
* I'm not sure if other projects include RPMs (versus tgz) in convenience 
binaries or not. It is helpful for ambari installs for sure. I verified that 
the server RPM includes the LICENSE & NOTICE files.  The traf_ambari RPM does 
contain a LICENSE file, but not a NOTICE. 

I checked:
* signatures
* checksums
* compared source to git tag
* DISCLAIMER, NOTICE, LICENSE, README
* Ran RAT
* Built source

--Steve

> -----Original Message-----
> From: Sandhya Sundaresan [mailto:[email protected]]
> Sent: Wednesday, March 22, 2017 10:54 AM
> To: [email protected]
> Subject: [VOTE] Apache Trafodion release 2.1.0 ready for release - 
> release candidate 1
> 
> Hi to everyone in the Trafodion Community,
> 
> This is a call to vote on release 2.1.0 of Apache Trafodion (incubating).
> Once the community approves a release candidate, a similar vote will 
> be taken in the Apache Incubator community.
> 
> This is a major release and includes over 300 fixes and some important 
> features. The highlights are all documented here:
> https://cwiki.apache.org/confluence/display/TRAFODION/Release+2.1
> They include :
> 
>   *   The new python installer
>   *   Ambari integration and much easier  install option for use on HDP
> platform
>   *   New features, SQL functions and syntax extensions
>   *   Performance enhancements
>   *   Bug fixes
> 
> JIRA Release Notes :
> Trafodion 2.1 JIRA Release
> Notes<https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=1
> 23 35704&styleName=Html&projectId=12318620&Create=Create&atl_token=A
> 5KQ-2QAV-T4JA-
> FDED%7Cfd60b9cef974c1fc62eab72a2c84777fbbcd084e%7Clin>
> Highlights :
> https://cwiki.apache.org/confluence/display/TRAFODION/Release+2.1
> 
> GIT info:
> The tag for this candidate is "2.1.0rc1". Git repository: git:// 
> git.apache.org/incubator-trafodion.git
> 
> Release artifacts :
> https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2
> .1.0-
> RC1/
> Artifacts are signed with my key :  85F0776A  which is in 
> https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS
> 
> Instructions :
> 
> Installing Trafodion using convenience binaries using the Python 
> installer or install with Ambari :
> http://trafodion.incubator.apache.org/docs/provisioning_guide/index.ht
> ml
> 
> Setting up build environment and building from source :
> https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Env
> i
> ronment
> https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source
> 
> [ ] +1 approve
> 
> [ ] +0 no opinion
> 
> [ ] -1 disapprove (and reason why)
> 
> Vote will be open until the community has had a chance to try out the 
> instructions and we get sufficient feedback  ( at least 72 hours), 
> unless cancelled.
> 

Reply via email to