The yarn issue on uno with java 11 has been fixed. Uno now puts
javax.activation-api on Hadoop's class path, and everything works
fine.

On Mon, Jun 17, 2019 at 12:22 PM Keith Turner <[email protected]> wrote:
>
> I have been running a new test[1] against this rc and things have been
> going well so far.  I have only been running on a single node.  I plan
> to run different test on a EC2 cluster this week using this RC
>
> I tried using Java 11 to run the test, but yarn would not start (using
> Apache hadoop 3.2.0).  I looked into that issue for a while and
> finally gave up went back to Java 8.
>
> [1]: https://github.com/apache/accumulo-testing/pull/81
>
> On Sun, Jun 9, 2019 at 10:33 PM Christopher <[email protected]> wrote:
> >
> > THIS IS A TEST. No vote is necessary. As a test, I've prepared a test
> > build of 2.0.0. If this were a real vote, the rest of this email would
> > apply. Since this is merely a test, you do not need to respond. You
> > can, however (and are encouraged to do so), use the staged test
> > artifacts to perform any testing you may wish to do in advance of a
> > real release candidate, which I hope to prepare this week, if the
> > community is ready for it.
> >
> > -----BEGIN GENERATED MESSAGE (if this were a real vote, which it isn't)-----
> >
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 2.0.0.
> >
> > Git Commit:
> >     e795d279b42f94a5b60cf6c5f91467874144cd61
> > Branch:
> >     2.0.0-rc0
> >
> > If this vote passes, a gpg-signed tag will be created using:
> >     git tag -f -m 'Apache Accumulo 2.0.0' -s rel/2.0.0 \
> >     e795d279b42f94a5b60cf6c5f91467874144cd61
> >
> > Staging repo: 
> > https://repository.apache.org/content/repositories/orgapacheaccumulo-1079
> > Source (official release artifact):
> > https://repository.apache.org/content/repositories/orgapacheaccumulo-1079/org/apache/accumulo/accumulo/2.0.0/accumulo-2.0.0-src.tar.gz
> > Binary: 
> > https://repository.apache.org/content/repositories/orgapacheaccumulo-1079/org/apache/accumulo/accumulo/2.0.0/accumulo-2.0.0-bin.tar.gz
> >
> > Append ".asc" to download the cryptographic signature for a given artifact.
> > (You can also append ".sha1" or ".md5" instead in order to verify the 
> > checksums
> > generated by Maven to verify the integrity of the Nexus repository
> > staging area.)
> >
> > Signing keys are available at https://www.apache.org/dist/accumulo/KEYS
> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> >
> > In addition to the tarballs and their signatures, the following checksum
> > files will be added to the dist/release SVN area after release:
> > accumulo-2.0.0-src.tar.gz.sha512 will contain:
> > SHA512 (accumulo-2.0.0-src.tar.gz) =
> > 897e324379e2350b618c79fa1adcd4f442328e09a5bea5020858dd4e7a4fe1268331a7d169c1d75fb1dfd96f7da0b9ca201ba76962df07a792bc739a8921da9e
> > accumulo-2.0.0-bin.tar.gz.sha512 will contain:
> > SHA512 (accumulo-2.0.0-bin.tar.gz) =
> > b8e32c02b7a9916f4a8eab3aaa762041d32a5e5578addfb4bb472a61816a379c2336ff775d19131920eea7c4e6d71cf0683a082fa4b3b1dd7cf4e666ea44f67d
> >
> > Release notes (in progress) can be found at:
> > https://accumulo.apache.org/release/accumulo-2.0.0/
> >
> > Release testing instructions:
> > https://accumulo.apache.org/contributor/verifying-release
> >
> > Please vote one of:
> > [ ] +1 - I have verified and accept...
> > [ ] +0 - I have reservations, but not strong enough to vote against...
> > [ ] -1 - Because..., I do not accept...
> > ... these artifacts as the 2.0.0 release of Apache Accumulo.
> >
> > This vote will remain open until at least Thu 13 Jun 2019 02:30:00 AM UTC.
> > (Wed 12 Jun 2019 10:30:00 PM EDT / Wed 12 Jun 2019 07:30:00 PM PDT)
> > Voting can continue after this deadline until the release manager
> > sends an email ending the vote.
> >
> > Thanks!
> >
> > P.S. Hint: download the whole staging repo with
> >     wget -erobots=off -r -l inf -np -nH \
> >     
> > https://repository.apache.org/content/repositories/orgapacheaccumulo-1079/
> >     # note the trailing slash is needed

Reply via email to