https://issues.apache.org/jira/browse/HBASE-14962

Is still rearing its ugly head on me. TestSplitWalDataLoss fails on me
every 1/4 times.

On Tue, Jan 5, 2016 at 12:34 PM, Sean Busbey <bus...@cloudera.com> wrote:

> Anyone have objections to including the proc-v2 admin tasks Stephen
> mentions?
>
> I should have time tonight to spin an updated RC. These changes seem
> relatively isolated. Anyone currently testing that would oppose me keeping
> the same closing date for the updated candidate?
>
> On Tue, Jan 5, 2016 at 2:09 PM, Stephen Jiang <syuanjiang...@gmail.com>
> wrote:
>
> > The administrative tasks for proc-v2 (5 JIRAs:  HBASE-14107, HBASE-14108,
> > HBASE-14487, HBASE-14488, and HBASE-14432) would be useful for debugging
> > or unblocking hanging procedures in master DDL.  The change is local and
> > low risk.  Discussing with Sean and Matteo privately, they agreed to
> > include them in 1.2.  I will commit to branch-1.2 today so that the next
> > 1.2RC would have the changes.
> >
> > thanks
> > Stephen
> >
> >
> >
> > On Mon, Jan 4, 2016 at 3:16 PM, Ted Yu <yuzhih...@gmail.com> wrote:
> >
> >> +1
> >>
> >> Ran unit test suite
> >> Exercised basic shell commands
> >>
> >> [INFO] BUILD SUCCESS
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Total time: 01:44 h
> >> [INFO] Finished at: 2016-01-03T09:12:35-08:00
> >>
> >> On Sun, Jan 3, 2016 at 4:29 AM, Sean Busbey <bus...@apache.org> wrote:
> >>
> >> > Happy New Year everyone! I'm pleased to announce the first release
> >> > candidate for HBase 1.2.0.
> >> >
> >> > Artifacts are available here:
> >> >
> >> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.0RC0/
> >> >
> >> > As of this vote, the relevant md5 hashes are:
> >> > 41c499a325ae6449fe99bbe315d07e10  hbase-1.2.0-bin.tar.gz
> >> > 537874610f1b53d4bce9d8a925661246  hbase-1.2.0-src.tar.gz
> >> >
> >> > Maven artifacts are also available in the staging repository:
> >> >
> >> >
> https://repository.apache.org/content/repositories/orgapachehbase-1122/
> >> >
> >> > artifacts are signed with my code signing key 0D80DB7C, available in
> >> > the project KEYS file:
> >> >
> >> > http://www.apache.org/dist/hbase/KEYS
> >> >
> >> > these artifacts correspond to commit hash
> >> >
> >> > 20c4368065165ad49bdfe8172316e42566a6d6a0
> >> >
> >> > which signed tag 1.2.0RC0 currently points to
> >> >
> >> >
> >> >
> >>
> https://git1-us-west.apache.org/repos/asf?p=hbase.git;a=tag;h=771e13960cf406185bb29447dffb6f2b5a56baec
> >> >
> >> > HBase 1.2.0 is the second minor release in the HBase 1.x line,
> >> continuing
> >> > on
> >> > the theme of bringing a stable, reliable database to the Hadoop and
> >> NoSQL
> >> > communities. This release includes roughly 250 resolved issues not
> >> covered
> >> > by previous 1.x releases.
> >> >
> >> > Notable new features include:
> >> > - JDK8 is now supported
> >> > - Hadoop 2.6.1+ and Hadoop 2.7.1+ are now supported
> >> > - per column-family time ranges for scan (HBASE-14355)
> >> > - daemons respond to SIGHUP to reload configs (HBASE-14529)
> >> > - region location methods added to thrift2 proxy (HBASE-13698)
> >> > - table-level sync that sends deltas (HBASE-13639)
> >> > - client side metrics via JMX (HBASE-12911)
> >> >
> >> > The full list of issues can be found at:
> >> >
> >> >
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12332062
> >> >
> >> > Please take a few minutes to verify the release[1] and vote on
> releasing
> >> > it:
> >> >
> >> > [ ] +1 Release this package as Apache HBase 1.2.0
> >> > [ ] +0 no opinion
> >> > [ ] -1 Do not release this package because...
> >> >
> >> > Vote will be subject to Majority Approval[2] and will close at 8:00PM
> >> > UTC on Monday, Jan 11th, 2016[3].
> >> >
> >> > [1]: http://www.apache.org/info/verification.html
> >> > [2]: https://www.apache.org/foundation/glossary.html#MajorityApproval
> >> > [3]: to find this in your local timezone see:
> >> > http://s.apache.org/hbase-1.2.0-rc0-close
> >> >
> >>
> >
> >
>
>
> --
> Sean
>

Reply via email to