[jira] [Resolved] (HBASE-22540) [Memstore] Correct counters in MemStoreChunkPool

2019-06-04 Thread Reid Chan (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-22540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan resolved HBASE-22540. --- Resolution: Fixed Hadoop Flags: Reviewed > [Memstore] Correct counters in MemStoreChunkPool >

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Guanghao Zhang
> > So what was in the 85MB file? I’m confused about the nature of the mistake > that caused it. > There are very duplicate content. Every issue's release note repeated hundreds of times. So it may be heplful to check this in precommit job. Grep the issue number from release note and check whether

[jira] [Created] (HBASE-22541) Backport HBASE-22160 "Add sorting functionality in regionserver web UI for user regions" to branch-1

2019-06-04 Thread Toshihiro Suzuki (JIRA)
Toshihiro Suzuki created HBASE-22541: Summary: Backport HBASE-22160 "Add sorting functionality in regionserver web UI for user regions" to branch-1 Key: HBASE-22541 URL:

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Sean Busbey
Busbey-MBA:hbase busbey$ git show cb0e9bb95599 | grep "Release Notes" | sort -u # HBASE 2.2.0 Release Notes Busbey-MBA:hbase busbey$ git show 61e9de9b82a9 | grep "Release Notes" | sort -u # HBASE 2.2.0 Release Notes Busbey-MBA:hbase busbey$ git checkout branch-2.2 Switched to branch 'branch-2.2'

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Misty Linville
So what was in the 85MB file? I’m confused about the nature of the mistake that caused it. On Tue, Jun 4, 2019 at 1:10 PM Sean Busbey wrote: > changelog is a list of all the fixes. release notes is supposed to be > the things we as a community think downstream users need to pay > attention to.

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Sean Busbey
changelog is a list of all the fixes. release notes is supposed to be the things we as a community think downstream users need to pay attention to. The release notes in an archive should be related to the release in question. Historically that has meant "all the maintenance releases in this minor

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Misty Linville
I’m confused how an automatically generated file can vary so much in size. Can the release notes file with an archive just target the release in question and leave off the older stuff? What’s the difference in practice between the release noted and changelog? A pre-commit and possibly a presubmit

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Andrew Purtell
The various release notes and changes.txt come up frequently in a listing of large-ish objects committed in the repo, along with autogenerated protobuf and thrift files. It's fine if we tolerate them all in return for something. Not requiring local IDL compilers to build is a reasonable tradeoff

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Sean Busbey
presuming you mean the two files from your original email: cb0e9bb95599 86MiB RELEASENOTES.md 61e9de9b82a9 14MiB RELEASENOTES.md these are both for HBase 2.2.0. Since branch-2.2 currently shows: Busbey-MBA:hbase busbey$ git checkout branch-2.2 Already on 'branch-2.2' Your branch is up to

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Andrew Purtell
There's an 80 MB release notes file, possibly a mistake; the next largest object is an 11 MB release notes file. Also a mistake? On Tue, Jun 4, 2019 at 10:11 AM Sean Busbey wrote: > Currently putting them in the repo is how we get release notes into the > source and binary artifacts we vote on.

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Sean Busbey
Currently putting them in the repo is how we get release notes into the source and binary artifacts we vote on. It's really convenient for making sure folks who download things have some version of the notes. We've been including the bare file in the dist area as well, so we'd face the same issue

Re: Someone checked in 85.80 MB RELEASENOTES.md

2019-06-04 Thread Andrew Purtell
What do you think about linking to a remote site-based release notes file instead of checking them into the main repo? On Mon, Jun 3, 2019 at 10:12 PM Guanghao Zhang wrote: > Sorry. This large RELEASENOTES.md may be introduced by me. I committed a > big RELEASENOTES.md to branch-2.2 yesterday.

[RESULT][VOTE] The first HBase 2.1.5 release candidate (RC1) is available for test

2019-06-04 Thread Stack
With 10+1s (about half binding), this VOTE passes. Let me push out the release. Thank you all for the the enthusiastic vote. Its great. S On Wed, May 29, 2019 at 8:59 AM Stack wrote: > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache HBase 2.1.5 > [

[jira] [Created] (HBASE-22540) [Memstore] Correct counters in MemStoreChunkPool

2019-06-04 Thread Reid Chan (JIRA)
Reid Chan created HBASE-22540: - Summary: [Memstore] Correct counters in MemStoreChunkPool Key: HBASE-22540 URL: https://issues.apache.org/jira/browse/HBASE-22540 Project: HBase Issue Type:

[jira] [Created] (HBASE-22539) Potential WAL corruption due to Unsafe.copyMemory usage when DBB are in place

2019-06-04 Thread Wellington Chevreuil (JIRA)
Wellington Chevreuil created HBASE-22539: Summary: Potential WAL corruption due to Unsafe.copyMemory usage when DBB are in place Key: HBASE-22539 URL: https://issues.apache.org/jira/browse/HBASE-22539

[VOTE] The fifth HBase 2.2.0 release candidate (RC5) is available

2019-06-04 Thread Guanghao Zhang
Please vote on this release candidate (RC) for Apache HBase 2.2.0. This is the first release of the branch-2.2 line. The VOTE will remain open for at least 72 hours. [] +1 [] +0/-0 [] -1 Do not release this package because ... The tag to be voted on is 2.2.0-RC5. The release files, including

Re: [VOTE] The first HBase 2.1.5 release candidate (RC1) is available for test

2019-06-04 Thread Balazs Meszaros
+1 - signatures, checksums: OK - rat check: OK - built from source (8u112): OK - unit tests (8u112): OK - ltt with 1M rows: OK - shell and web UI: OK On Fri, May 31, 2019 at 9:38 AM OpenInx wrote: > +1 (non-binding) > > Run the hbase-vote.sh, looks good to me. > * Signature: ok >

[jira] [Created] (HBASE-22538) Prevent graceful_stop.sh from shutting down RS too early before finishing unloading regions

2019-06-04 Thread Jeongdae Kim (JIRA)
Jeongdae Kim created HBASE-22538: Summary: Prevent graceful_stop.sh from shutting down RS too early before finishing unloading regions Key: HBASE-22538 URL: https://issues.apache.org/jira/browse/HBASE-22538

[jira] [Created] (HBASE-22537) Split happened Replica region can not be deleted after deleting table successfully and restarting RegionServer

2019-06-04 Thread Y. SREENIVASULU REDDY (JIRA)
Y. SREENIVASULU REDDY created HBASE-22537: - Summary: Split happened Replica region can not be deleted after deleting table successfully and restarting RegionServer Key: HBASE-22537 URL: