[jira] [Created] (HBASE-20167) Optimize the implementation of ReplicationSourceWALReader

Duo Zhang created HBASE-20167: - Summary: Optimize the implementation of ReplicationSourceWALReader Key: HBASE-20167 URL: https://issues.apache.org/jira/browse/HBASE-20167 Project: HBase Issue

Re: [VOTE] Merge branch HBASE-19397 back to master and branch-2.

Since branch-2.0 has been cut and branch-2 is now 2.1.0-SNAPSHOT, will merge branch HBASE-19397-branch-2 back to branch-2. 2018-01-10 9:20 GMT+08:00 张铎(Duo Zhang) : > If branch-2.0 will be out soon then let's target this to 2.1. No problem. > > Thanks. > > 2018-01-10 1:28

[jira] [Created] (HBASE-20166) Make sure the RS/Master can works fine when using table based replication storage layer

Zheng Hu created HBASE-20166: Summary: Make sure the RS/Master can works fine when using table based replication storage layer Key: HBASE-20166 URL: https://issues.apache.org/jira/browse/HBASE-20166

[jira] [Created] (HBASE-20165) Shell command to make a normal peer to be a serial replication peer

Zheng Hu created HBASE-20165: Summary: Shell command to make a normal peer to be a serial replication peer Key: HBASE-20165 URL: https://issues.apache.org/jira/browse/HBASE-20165 Project: HBase

[jira] [Created] (HBASE-20164) failed hadoopcheck should add footer link

Mike Drob created HBASE-20164: - Summary: failed hadoopcheck should add footer link Key: HBASE-20164 URL: https://issues.apache.org/jira/browse/HBASE-20164 Project: HBase Issue Type: Bug

Re: [ANNOUNCE] New HBase committer Zach York

Thanks everyone! I am excited to continue my work in HBase! Thanks, Zach On Thu, Mar 8, 2018 at 9:03 AM, ramkrishna vasudevan < ramkrishna.s.vasude...@gmail.com> wrote: > Congratulations Zach !!! > > On Thu, Mar 8, 2018 at 11:03 AM, Yu Li wrote: > > > Congratulations, Zach!

[DISCUSS] our stable release pointer and EOM

Hi folks! I've been working to get the test suite back to green on branch-1.2; we have a lot of branches to track backport for and a non-trivial amount of tech debt across all of them from the nightlies being offline. After the stable pointer moves forward from branch-1.2 I'll keep doing RM duty

[jira] [Created] (HBASE-20163) Disable major compaction when standby cluster replay the remote wals

Guanghao Zhang created HBASE-20163: -- Summary: Disable major compaction when standby cluster replay the remote wals Key: HBASE-20163 URL: https://issues.apache.org/jira/browse/HBASE-20163 Project:

[jira] [Resolved] (HBASE-16005) Implement HFile ref's tracking (bulk loading) in ReplicationQueuesHBaseImpl and ReplicationQueuesClientHBaseImpl

[ https://issues.apache.org/jira/browse/HBASE-16005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu resolved HBASE-16005. -- Resolution: Duplicate > Implement HFile ref's tracking (bulk loading) in ReplicationQueuesHBaseImpl >

[jira] [Created] (HBASE-20162) [nightly] depending on pipeline execution we sometimes refer to the wrong workspace

Sean Busbey created HBASE-20162: --- Summary: [nightly] depending on pipeline execution we sometimes refer to the wrong workspace Key: HBASE-20162 URL: https://issues.apache.org/jira/browse/HBASE-20162

Re: DISCUSSION: "branch RM" roles for non-released branches branch-1, branch-2, and master

For the number of patch release, I think it depends on the speed we add new features. The more features contained in a minor release, the more patch releases we need. Of course a responsible RM will also trigger more releases. What I want to say is, we do not need to set a hard limit on the

Re: Apache Hbase | Requesting for Invite |

Hi Shiva, Anyone is free to contribute to Apache HBase; just open a JIRA, submit a patch, and work with a committer to get it incorporated into the project. No ICLA is needed to contribute to the project. Over time, contributors who positively impact the project may be invited to become

[jira] [Resolved] (HBASE-15151) Rely on nightly tests for findbugs compliance on existing branch

[ https://issues.apache.org/jira/browse/HBASE-15151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-15151. - Resolution: Fixed > Rely on nightly tests for findbugs compliance on existing branch >

[jira] [Created] (HBASE-20161) disable HBase-Trunk_matrix job

Sean Busbey created HBASE-20161: --- Summary: disable HBase-Trunk_matrix job Key: HBASE-20161 URL: https://issues.apache.org/jira/browse/HBASE-20161 Project: HBase Issue Type: Task

Re: DISCUSSION: "branch RM" roles for non-released branches branch-1, branch-2, and master

The Phoenix project typically releases new minors. Patch releases are rare. This used to be our model too before 1.0. (For the 0.x.y versions mentally drop the "0.") Users don't seem to care. I do think there is appetite for one or two long term stable code lines. Right now that's

Re: [ANNOUNCE] New HBase committer Peter Somogyi

Keep up your good work Peter!! On Thu, Mar 8, 2018 at 3:45 AM, Mike Drob wrote: > Welcome, Peter! > > On Fri, Feb 23, 2018 at 7:51 AM, Anoop John wrote: > > > Congrats Peter.. > > > > Anoop > > > > > > On Friday, February 23, 2018, ramkrishna vasudevan

Re: [ANNOUNCE] New HBase committer Zach York

Congratulations Zach !!! On Thu, Mar 8, 2018 at 11:03 AM, Yu Li wrote: > Congratulations, Zach! > > Best Regards, > Yu > > On 8 March 2018 at 06:13, Mike Drob wrote: > > > Congratulations, Zach! > > > > On Wed, Mar 7, 2018 at 4:03 PM, Andrew Purtell

Re: [DISCUSS] strategy on Java versions

bq. Dropping all but LTS on major version +1 to the above initiative. On Thu, Mar 8, 2018 at 8:37 AM, Josh Elser wrote: > Oof, more to do, but I think the list you put together is a good plan to > start. Dropping all but LTS on major version sounds good as well. > > Thanks

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

+1 I would also be supportive of ripping it all out for the reasons that Andrew already stated. On 3/6/18 3:22 PM, Stack wrote: 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

Re: [DISCUSS] strategy on Java versions

Oof, more to do, but I think the list you put together is a good plan to start. Dropping all but LTS on major version sounds good as well. Thanks for thinking about this already. On 3/6/18 12:20 PM, Sean Busbey wrote: Hi folks! Our ref guide section on Java versions[1] is starting to look

Re: Building Trunk

Hum. mvn clean and rebuild passed. Strange. forget about that. Thanks. 2018-03-08 9:51 GMT-05:00 Jean-Marc Spaggiari : > Hi all, > > Trying to build Trunk I'm getting the following error: > [INFO] - > [ERROR]

Building Trunk

Hi all, Trying to build Trunk I'm getting the following error: [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR]

Re: DISCUSSION: "branch RM" roles for non-released branches branch-1, branch-2, and master

> frequent. For example, I'm going to be done with branch-1.4 in six months > and on to branch-1.5. (Hypothetically.) Anyone is welcome to RM those > branch-x.y. As long as someone is actively RMing branch-x.y it stays alive. > That's how we'd come to a consensus on what is long term stable. I

Re: DISCUSSION: "branch RM" roles for non-released branches branch-1, branch-2, and master

So to sum up my understanding of the idea: - More minor/major releases, less patch releases - From logistic perspective, we are moving from a model where few people are locked in for long time (4-5 RMs locked in for ~10 patch releases) to a model where more people are locked in for less time (more

[jira] [Created] (HBASE-20160) TestRestartCluster.testRetainAssignmentOnRestart uses the wrong condition to decide whether the assignment is finished

Duo Zhang created HBASE-20160: - Summary: TestRestartCluster.testRetainAssignmentOnRestart uses the wrong condition to decide whether the assignment is finished Key: HBASE-20160 URL: