hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashish Singhi <ashishsin...@apache.org>
Subject Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available
Date Sat, 10 Jun 2017 08:35:44 GMT
Its not an issue. The log warnings are coming by HBASE-9393 patch. If user
Hadoop version is not 2.6.4+ or 2.7.0+ then this warn message will be
logged, notifying user about a CLOSE_WAIT connection left behind. As this
log message is in common code flow of read, should we up the log level to
avoid too many same warnings ?

Regards,
Ashish

On Fri, Jun 9, 2017 at 10:45 AM, Stack <stack@duboce.net> wrote:

> Oh, maybe file issues for what you found boss?
> St.Ack
>
> On Thu, Jun 8, 2017 at 10:15 PM, Stack <stack@duboce.net> wrote:
>
> > Thanks Umesh!
> >
> > On Thu, Jun 8, 2017 at 2:36 PM, Umesh Agashe <uagashe@cloudera.com>
> wrote:
> >
> >> +1
> >>
> >> - Downloaded the src tarball.
> >>   - Verified the checksums and signature. Looks good.
> >>   - Built from source. openjdk version "1.8.0_102"
> >>   - mvn apache-rat:check   Passed
> >>
> >> - Download the bin tarball.
> >>   - Verified the checksums and signature. Looks good.
> >>   - Extracted it. Layout looks good.
> >>   - Started a local instance. Ran the 'hbase shell' with some basic
> table
> >> commands. Looks good.
> >>   - Ran ltt with 10 million rows and 2 columns/ row
> >>
> >> Note:
> >>   - Did not run unit tests. There are a problems with the build. See:
> >> https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(lat
> >> est),label=Hadoop/10/console
> >>   - Noticed a few errors in the log file like:
> >> WARN  [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke
> >> 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream
> .
> >> So there may be a TCP socket connection left open in CLOSE_WAIT state.
> >>
> >>
> >> On Thu, Jun 8, 2017 at 8:33 AM, Stack <stack@duboce.net> wrote:
> >>
> >> > On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey <busbey@apache.org>
> wrote:
> >> >
> >> > > The minimum voting period is 72 hours for a PMC to bless a release.
> >> > > Can we aim for that?
> >> > >
> >> > >
> >> > Sure (Stickler!)
> >> > St.Ack
> >> >
> >> >
> >> >
> >> > > On Thu, Jun 8, 2017 at 2:33 AM, Stack <stack@duboce.net> wrote:
> >> > > > The first release candidate for HBase 2.0.0-alpha-1 is up at:
> >> > > >
> >> > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alp
> >> ha-1RC0/
> >> > > >
> >> > > > Maven artifacts are available from a staging directory here:
> >> > > >
> >> > > >  https://repository.apache.org/content/repositories/
> >> > orgapachehbase-1169
> >> > > >
> >> > > > All was signed w/ my key 8ACC93D2
> >> > > > <http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2>
> >> > > >
> >> > > > I tagged the RC as 2.0.0-alpha-1RC0
> >> > > > (c830a0f47f58d4892dd3300032c8244d6278aecc).
> >> > > >
> >> > > > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a
rough
> >> cut
> >> > > > ('alpha') not-for-production preview of what hbase-2.0.0 will
look
> >> > like.
> >> > > It
> >> > > > is what we used to call a 'Developer' release[1] meant mostly
for
> >> devs
> >> > > and
> >> > > > downstreamers to test drive and flag us early if we there are
> issues
> >> > > we’ve
> >> > > > missed ahead of our rolling a production-worthy release.
> >> > > >
> >> > > > hbase-2.0.0 includes a fleet of new features that include a new
> >> > > assignment
> >> > > > manager, means for keeping read and write path off-heap, in-memory
> >> > > > compactions, and more. I have been keeping a running doc on the
> >> state
> >> > of
> >> > > > 2.0.0 here [2]. There is much to do still (see aforementioned
> doc).
> >> > > >
> >> > > > The list of features addressed in 2.0.0 so far can be found here
> >> [4].
> >> > > There
> >> > > > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can
be
> >> > found
> >> > > > here [3].
> >> > > >
> >> > > > Please take it for a spin and vote on whether it ok to put out
as
> >> our
> >> > > first
> >> > > > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24
> >> hours.
> >> > > >
> >> > > > Thanks,
> >> > > > St.Ack
> >> > > >
> >> > > > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> >> > > > 2.
> >> > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> >> > > ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> >> > > > 3.
> >> > > > https://issues.apache.org/jira/browse/HBASE-17852?jql=
> >> > > project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
> >> > > 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
> >> > > 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
> >> > > 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
> >> > > 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
> >> > > 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
> >> > > 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
> >> > > 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%
> 20Available%22)
> >> > > > 4.
> >> > > > https://issues.apache.org/jira/browse/HBASE-18191?jql=
> >> > > project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
> >> > > 202.0.0)%20and%20(status%20%3D%20Resolved)
> >> > >
> >> >
> >>
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message