With 3 +1 votes and no 0 or -1 votes, this vote has passed. I will process
these artifacts for distribution as 1.1.3 momentarily. Thanks again for
everyone who took time to review the candidates this release.
Thanks,
Nick
On Mon, Jan 25, 2016 at 9:40 PM, Nick Dimiduk <ndimi...@apache.org> wrote:
> +1
>
> - verified tarballs vs public key in p.a.o/keys/committers/ndimiduk.asc.
> - extracted bin tgz:
> - inspect structure. look good.
> - run LoadTestTool against standalone built from src tgz with FAST_DIFF
> block encoder and ROWCOL blooms. No issues, logs look good.
> - poked around webUI. looks good.
> - load the site, browsed book and API docs.
> - extracted src tgz:
> - built, ran tests; filed a couple subtasks under HBASE-15168
> - inspect structure. look good.
> - run LoadTestTool against standalone built from src tgz with FAST_DIFF
> block encoder and ROWCOL blooms. No issues, logs look good.
> - poked around webUI. looks good.
> - inspected compatibility report. Issues look acceptable as per our
> policies.
>
> On Mon, Jan 25, 2016 at 7:16 PM, Nick Dimiduk <ndimi...@apache.org> wrote:
>
>> Yes Andrew, that's my conclusion as well. I will evaluate the bits for
>> myself this evening. I'll also dig into the test results from my weekend
>> runs.
>>
>>
>> On Monday, January 25, 2016, Andrew Purtell <apurt...@apache.org> wrote:
>>
>>> Hi Nick,
>>>
>>> Perhaps the silence in response to your inquiry and lack of vetos to date
>>> can be interpreted as consensus to move forward. There are 2 +1 votes
>>> already. If you decide to cast a third positive vote, we can release.
>>>
>>>
>>> On Thu, Jan 21, 2016 at 2:32 PM, Nick Dimiduk <ndimi...@apache.org>
>>> wrote:
>>>
>>> > > TestDurability is failing in branch-1.1 with a small issue and have
>>> just
>>> > filed HBASE-15150 to fix it, JFYI.
>>> >
>>> > Thanks a lot Yu Li, I'll take a look.
>>> >
>>> > > I'm seeing that TestDurability failure as well, and am also finding
>>> that
>>> > TestWALLockup frequently times out and fails when running the unit test
>>> > suite with 7u79.
>>> >
>>> > Thanks for checking guys. This release line has not had the diligent
>>> > attention to test stability that later branches have. Indeed this
>>> point was
>>> > raised around earlier release from this branch as well. Previously we
>>> were
>>> > simply disabling flakey tests on this branch as bandwidth was not
>>> available
>>> > to fix them and they withheld release. I've depended more on CM
>>> testing to
>>> > verify bits and less on UT harness with far with branch-1.1. It is my
>>> > intention to organize efforts around backporting test fixes (ie,
>>> > from HBASE-14420), though I see no reason to withhold further patch
>>> > releases in the mean time. This patch release is *months* over due.
>>> >
>>> > I am of course acting on the PMC's behalf as release manager. I will
>>> defer
>>> > to the PMC judgement on whether this UT situation constitutes
>>> acceptable
>>> > parameters for release. I will absolutely accept community assistance
>>> in
>>> > bring this branch's UT runs back into the green; it's not an effort I'm
>>> > able to tackle solo in any timely manor.
>>> >
>>> > -n
>>> >
>>> > On Thu, Jan 21, 2016 at 11:36 AM, Andrew Purtell <apurt...@apache.org>
>>> > wrote:
>>> >
>>> > > I'm seeing that TestDurability failure as well, and am also finding
>>> that
>>> > > TestWALLockup frequently times out and fails when running the unit
>>> test
>>> > > suite with 7u79.
>>> > >
>>> > > The LICENSE.txt file in the binary tarball has some unsubstituted
>>> > > "${dep.licenses[0].comments}" for Apache Commons Collections and
>>> Netty. I
>>> > > think this is only a nit because right above where the substitutions
>>> fail
>>> > > we indicate in both cases the dependency is ASL 2.0 licensed and the
>>> text
>>> > > of that license appears elsewhere in the file.
>>> > >
>>> > > I'll defer to the RM if the above should sink the RC.
>>> > >
>>> > > Otherwise,
>>> > > - Signatures and checksums look good
>>> > > - Tarball structure looks good
>>> > > - Build from source with release auditing enabled passes
>>> > > - Ran LTT against a minicluster, loaded 1M rows (and updating 20%),
>>> no
>>> > > errors, no unusual or unexpected messages in the logs, and reported
>>> > > latencies are roughly as expected
>>> > >
>>> > > +1
>>> > >
>>> > >
>>> > >
>>> > > On Thu, Jan 21, 2016 at 5:23 AM, Yu Li <car...@gmail.com> wrote:
>>> > >
>>> > > > Hi Nick,
>>> > > >
>>> > > > TestDurability is failing in branch-1.1 with a small issue and have
>>> > just
>>> > > > filed HBASE-15150 to fix it, JFYI.
>>> > > >
>>> > > > Best Regards,
>>> > > > Yu
>>> > > >
>>> > > > On 21 January 2016 at 06:33, Enis Söztutar <e...@apache.org>
>>> wrote:
>>> > > >
>>> > > > > Thanks Nick for putting the RC together.
>>> > > > >
>>> > > > > Here is my +1.
>>> > > > >
>>> > > > > - checked crcs, sigs.
>>> > > > >
>>> > > > > - checked tarball layouts, files, jar files, etc.
>>> > > > >
>>> > > > > - checked the book in the bin tar
>>> > > > >
>>> > > > > - checked versions reported
>>> > > > >
>>> > > > > - checked the compat report
>>> > > > >
>>> > > > > - compiled with Hadoop 2.3 to 2.7
>>> > > > >
>>> > > > > - build with hbase-downstreamer
>>> > > > >
>>> > > > > - run local model, shell smoke tests, LTT.
>>> > > > >
>>> > > > > - Put it up on a 4 node cluster, ran LTT.
>>> > > > >
>>> > > > >
>>> > > > > Everything looks nominal.
>>> > > > >
>>> > > > > Enis
>>> > > > >
>>> > > > > On Sat, Jan 16, 2016 at 8:06 PM, Nick Dimiduk <
>>> ndimi...@apache.org>
>>> > > > wrote:
>>> > > > >
>>> > > > > > After a short hiatus, I'm happy to announce the second release
>>> > > > candidate
>>> > > > > of
>>> > > > > > HBase 1.1.3 (HBase-1.1.3RC1) is available for download at
>>> > > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.3RC1/
>>> > > > > >
>>> > > > > > Maven artifacts are also available in the staging repository
>>> > > > > >
>>> > > >
>>> >
>>> https://repository.apache.org/content/repositories/orgapachehbase-1125/
>>> > > > > >
>>> > > > > > Artifacts are signed with my code signing subkey
>>> > 0xAD9039071C3489BD,
>>> > > > > > available in the Apache keys directory
>>> > > > > > https://people.apache.org/keys/committer/ndimiduk.asc
>>> > > > > >
>>> > > > > > The detailed source and binary compatibility report vs 1.1.0
>>> has
>>> > been
>>> > > > > > published for your review, at
>>> > > > > >
>>> http://home.apache.org/~ndimiduk/1.1.0_1.1.3RC1_compat_report.html
>>> > > > > >
>>> > > > > > HBase 1.1.3 is the third patch release in the HBase 1.1 line,
>>> > > > continuing
>>> > > > > on
>>> > > > > > the theme of bringing a stable, reliable database to the
>>> Hadoop and
>>> > > > NoSQL
>>> > > > > > communities. This release includes over 160 bug fixes since the
>>> > 1.1.2
>>> > > > > > release. Notable correctness fixes beyond RC0 include
>>> HBASE-14782,
>>> > > > > > HBASE-14840, HBASE-14989, HBASE-14822, HBASE-15035,
>>> HBASE-15031,
>>> > and
>>> > > > > > HBASE-15085.
>>> > > > > >
>>> > > > > > Also be aware that this release includes HBASE-14799, which
>>> closes
>>> > a
>>> > > > > remote
>>> > > > > > command execution vulnerability.
>>> > > > > >
>>> > > > > > The full list of fixes included in this release is available at
>>> > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12333152
>>> > > > > > and in the CHANGES.txt file included in the distribution.
>>> > > > > >
>>> > > > > > Please try out this candidate and vote +/-1 by 23:59 Pacific
>>> time
>>> > on
>>> > > > > > Friday, 2016-01-22 as to whether we should release these
>>> artifacts
>>> > as
>>> > > > > HBase
>>> > > > > > 1.1.3.
>>> > > > > >
>>> > > > > > Thanks,
>>> > > > > > Nick
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > Best regards,
>>> > >
>>> > > - Andy
>>> > >
>>> > > Problems worthy of attack prove their worth by hitting back. - Piet
>>> Hein
>>> > > (via Tom White)
>>> > >
>>> >
>>>
>>>
>>>
>>> --
>>> Best regards,
>>>
>>> - Andy
>>>
>>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>>> (via Tom White)
>>>
>>
>
