Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

+0, I didn't have enough time on this RC to run a more complete suite of tests like I was hoping for. sign/sums ok SHOULD NOT supply a MD5 checksum file (because MD5 is too broken). [1] compile src 8u151 ok compile src 8u151 w/ error-prone NOT OK - HBASE-19987 [1]:

Re: [NOTICE] branch-2 open for commits again but please get my ok before commit; thanks.

After release, hopefully in morning. Thanks for reminder. S On Tue, Mar 6, 2018 at 4:48 PM, 张铎(Duo Zhang) wrote: > So is it the time to cut branch-2.0? > > 2018-03-07 8:04 GMT+08:00 Stack : > > > On Tue, Mar 6, 2018 at 10:32 AM, Sean Busbey

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

I deployed it on 8 nodes, running many different things including MR, RowCounts, compactions, etc. Nothing new. So far so good... 2018-03-06 17:29 GMT-05:00 Stack : > On Tue, Mar 6, 2018 at 12:52 PM, Peter Somogyi > wrote: > > > +1 (non-binding) > > > > -

Re: [NOTICE] branch-2 open for commits again but please get my ok before commit; thanks.

So is it the time to cut branch-2.0? 2018-03-07 8:04 GMT+08:00 Stack : > On Tue, Mar 6, 2018 at 10:32 AM, Sean Busbey wrote: > > > Is branch-2 open again now? Sorry if I missed the all-clear but I > > could not find it. > > > > > I hadn't sent one. > > Was

[NOTICE] branch-2 open for commits again but please get my ok before commit; thanks.

On Tue, Mar 6, 2018 at 10:32 AM, Sean Busbey wrote: > Is branch-2 open again now? Sorry if I missed the all-clear but I > could not find it. > > I hadn't sent one. Was nervous watching my nightlies: https://builds.apache.org/job/HBase%20Nightly/job/branch-2/ Let me open it

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

On Tue, Mar 6, 2018 at 12:52 PM, Peter Somogyi wrote: > +1 (non-binding) > > - Signature, checksum OK > - Test suite using 1.8.0_161 OK > - Build and run from source OK > - Run from bin tarball OK > - PE 1M rows OK > - LTT 1M rows OK > - Basic operations from shell and Java

[jira] [Created] (HBASE-20143) Fix checkstyle introduced in parent in new test additions

stack created HBASE-20143: - Summary: Fix checkstyle introduced in parent in new test additions Key: HBASE-20143 URL: https://issues.apache.org/jira/browse/HBASE-20143 Project: HBase Issue Type:

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

+1 (non-binding) - Signature, checksum OK - Test suite using 1.8.0_161 OK - Build and run from source OK - Run from bin tarball OK - PE 1M rows OK - LTT 1M rows OK - Basic operations from shell and Java client OK One thing I noticed: CHANGES.txt isn't updated, latest information is about 0.93.0

[jira] [Resolved] (HBASE-16795) Revisit 'in project Maven repo' checked in as part of HBASE-14785

[ https://issues.apache.org/jira/browse/HBASE-16795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-16795. --- Resolution: Won't Fix Branch 1.1 is EOL > Revisit 'in project Maven repo' checked in as part of

[jira] [Resolved] (HBASE-15168) Zombie stomping branch-1.1 edition

[ https://issues.apache.org/jira/browse/HBASE-15168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-15168. --- Resolution: Won't Fix Branch 1.1 is EOL > Zombie stomping branch-1.1 edition >

[jira] [Resolved] (HBASE-15308) Flakey TestSplitWalDataLoss on branch-1.1

[ https://issues.apache.org/jira/browse/HBASE-15308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-15308. --- Resolution: Won't Fix Branch 1.1 is EOL > Flakey TestSplitWalDataLoss on branch-1.1 >

[jira] [Resolved] (HBASE-15185) Fix jdk8 javadoc warnings for branch-1.1

[ https://issues.apache.org/jira/browse/HBASE-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-15185. --- Resolution: Won't Fix Branch 1.1 is EOL > Fix jdk8 javadoc warnings for branch-1.1 >

Re: [DISCUSS] What should we bundle in our bin tarball?

Thanks lads. Let me look at purge of non-user javadocs and at building a javadoc-only artifiact (then could purge all javadoc as per Andy). S On Tue, Mar 6, 2018 at 11:45 AM, Sean Busbey wrote: > if we keep any javadocs in the tarball they should just be the user > facing

Re: [DISCUSS] strategy on Java versions

> -- "Recommended" for running > > I think we should suggest folks rely on LTS releases of Java, wether > from the OpenJDK project (which looks like it will be equivalent to > the Oracle version) or a vender. > > That would mean updating our support matrix to call out Java 9 and > Java 10 as "Not

Re: [DISCUSS] What should we bundle in our bin tarball?

if we keep any javadocs in the tarball they should just be the user facing javadocs (wether that includes testapidocs I could go either way). I'd be in favor of dumping the javadocs entirely from the binary tarball. do we know why the apidocs are bigger than our binaries? are we mistakingly

[jira] [Resolved] (HBASE-14341) branch-1.1 source assembly contains spurious hbase-shaded-client and hbase-shaded-server modules

[ https://issues.apache.org/jira/browse/HBASE-14341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-14341. --- Resolution: Won't Fix branch-1.1 is EOL > branch-1.1 source assembly contains spurious

[jira] [Created] (HBASE-20142) Copy master doc into branch-2 and edit to make it suit 2.0.0

stack created HBASE-20142: - Summary: Copy master doc into branch-2 and edit to make it suit 2.0.0 Key: HBASE-20142 URL: https://issues.apache.org/jira/browse/HBASE-20142 Project: HBase Issue Type:

Re: [DISCUSS] What should we bundle in our bin tarball?

> I could make it so we do not build dev doc by default or that we do not include it in our bin tarball? The binary tarball is so huge at this point I think getting the size down by pruning javadoc is reasonable, at least in the short term. We have javadocs up on our site. They will also be

[jira] [Created] (HBASE-20141) Fix TooManyFiles exception when RefreshingChannels in FileIOEngine

Zach York created HBASE-20141: - Summary: Fix TooManyFiles exception when RefreshingChannels in FileIOEngine Key: HBASE-20141 URL: https://issues.apache.org/jira/browse/HBASE-20141 Project: HBase

[DISCUSS] What should we bundle in our bin tarball?

On the vote thread for hbase-2.0.0-beta-2, it was noted that the bulk of our convenience bin tarball size is test javadoc [1] (~ > 50%). Should our bin tarball include all possible doc both api and dev api for both test and user? I could make it so we do not build dev doc by default or that we do

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

+1 (non-binding) Hadoop Pseudo-distrbibuted: 2.7.5 $M2_HOME from scratch Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) Maven home: /opt/maven/apache-maven-3.5.2 Java version: 1.8.0_161, vendor: Oracle Corporation Java home:

Re: Please hold on commits to branch-2; cutting an hbase-2.0.0-beta-2 Release Candidate

Is branch-2 open again now? Sorry if I missed the all-clear but I could not find it. On Thu, Mar 1, 2018 at 11:59 AM, Stack wrote: > Short Version: Please hold on making commits to branch-2. I am in the > process of cutting a hbase-2.0.0-beta-2 release candidate. It make take

[DISCUSS] strategy on Java versions

Hi folks! Our ref guide section on Java versions[1] is starting to look dated, because the Oracle version of Java 9 hits end of public updates this month and we don't mention it at all. I'd like to discuss how we want to approach keeping HBase up-to-date on new Java versions. As background, the

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

+1 (binding) * src release OK * xsums/sigs OK * Can build and run from src OK * Loaded some data locally On 3/2/18 6:40 PM, Stack wrote: The first release candidate for HBase 2.0.0-beta-2 is up at https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/ Maven artifacts are

docs review request HBASE-20072

Could a committer take a few minutes to review the changes here: https://issues.apache.org/jira/browse/HBASE-20072 1.1 has been EOM for coming up on 3 months and this jira updates our docs to better reflect that.

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

On 3/5/18 2:40 PM, Stack wrote: On Mon, Mar 5, 2018 at 6:56 AM, Chia-Ping Tsai wrote: +1 (binding) with some questions unit test (oracle jdk-8u161) - all pass deploy binary (3 nodes) - ok browse master/regionserver web - LGTM put/delete/get/scan 500W rows - ok

[jira] [Created] (HBASE-20140) HRegion FileSystem should be instantiated from hbase rootDir not default

Adrian Muraru created HBASE-20140: - Summary: HRegion FileSystem should be instantiated from hbase rootDir not default Key: HBASE-20140 URL: https://issues.apache.org/jira/browse/HBASE-20140 Project:

[jira] [Resolved] (HBASE-20126) Add UT for serial replication after region merge

[ https://issues.apache.org/jira/browse/HBASE-20126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-20126. --- Resolution: Duplicate > Add UT for serial replication after region merge >

[jira] [Created] (HBASE-20139) NPE in RSRpcServices.get() when getRegion throws an exception

Abhishek Singh Chouhan created HBASE-20139: -- Summary: NPE in RSRpcServices.get() when getRegion throws an exception Key: HBASE-20139 URL: https://issues.apache.org/jira/browse/HBASE-20139

[jira] [Created] (HBASE-20138) Find a way to deal with the conflicts when updating replication position

Duo Zhang created HBASE-20138: - Summary: Find a way to deal with the conflicts when updating replication position Key: HBASE-20138 URL: https://issues.apache.org/jira/browse/HBASE-20138 Project: HBase