[jira] [Created] (HBASE-20539) Disable IMC; part 2

stack created HBASE-20539: - Summary: Disable IMC; part 2 Key: HBASE-20539 URL: https://issues.apache.org/jira/browse/HBASE-20539 Project: HBase Issue Type: Sub-task Components:

[jira] [Resolved] (HBASE-20535) Check the UT TestSaslFanOutOneBlockAsyncDFSOutput which is always flaky

[ https://issues.apache.org/jira/browse/HBASE-20535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu resolved HBASE-20535. -- Resolution: Duplicate Close this, because [~stack] had handled it. > Check the UT

[jira] [Resolved] (HBASE-20505) PE should support multi column family read and write cases

[ https://issues.apache.org/jira/browse/HBASE-20505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-20505. Resolution: Fixed Pushed to 1.2 and up > PE should support multi column family read and

Re: [DISCUSS] Effective HBase in the Cloud

How do we deal with replication? It is file based... 2018-05-08 10:12 GMT+08:00 Josh Elser : > > > On 5/7/18 2:53 PM, Stack wrote: > >> On Thu, May 3, 2018 at 9:04 AM, Josh Elser wrote: >> >> Hi, >>> >>> ... I'm happy to delve some more into how I think we

Re: On the 2.1.0 and 3.0.0 release

Big big big +1 (Came in to say just this but you beat me to it :D) On 5/7/18 12:07 AM, 张铎(Duo Zhang) wrote: Let's do big features in 3.0.0 only. Ideally there will no big new features for a minor release, so that we can move the stable pointer to newer minor versions quickly and retire the

Re: [DISCUSS] Effective HBase in the Cloud

On 5/7/18 2:53 PM, Stack wrote: On Thu, May 3, 2018 at 9:04 AM, Josh Elser wrote: Hi, ... I'm happy to delve some more into how I think we can implement this. I'd be interested in this part. St.Ack You got it, boss. Let me find the time to get that document exported

Re: [DISCUSS] Effective HBase in the Cloud

Thanks for the read, Lars! That's a good question on the sequenceid part. Like my reply to Chia-Ping, I don't think I have a good answer at this point. I would assume that there could/should be common sequenceid logic across WAL implementations, but I'm not sure if it's better done as

Re: [DISCUSS] Effective HBase in the Cloud

Thanks for the read, Chia-Ping! I don't have a good answer for you at this point, but that's a good question. I think a significant part of the core WAL refactoring work will require us to work with all of the various WAL impls we're accruing :) * FSHWAL * AsyncWAL * WALLess * Ratis-WAL

Re: On the 2.1.0 and 3.0.0 release

On Mon, May 7, 2018 at 2:15 AM, Yu Li wrote: > bq. As I volunteered to be the release manager for the 2.1 release line > I guess we could expect another great release line (smile) > > Yep! > bq. For the 2.1 release line... > I could see more "Punted out of 2.0" features in

Re: [DISCUSS] Effective HBase in the Cloud

On Thu, May 3, 2018 at 9:04 AM, Josh Elser wrote: > Hi, > > ... I'm happy to delve some more into how I think we can implement this. > > I'd be interested in this part. St.Ack > - Josh > > [1] https://docs.google.com/document/d/1Su5py_T5Ytfh9RoTTX2s20Kb >

[ANNOUNCE] Apache HBase 1.4.4 is now available for download

​The HBase team is happy to announce the immediate availability of Apach​e HBase 1.4.4! Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. To

[jira] [Resolved] (HBASE-20537) The download link is not available in the downloads webpage

[ https://issues.apache.org/jira/browse/HBASE-20537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-20537. --- Resolution: Fixed Assignee: stack Pushed small change adding 'src' and or 'bin' text. Thanks

[jira] [Created] (HBASE-20538) TestSaslFanOutOneBlockAsyncDFSOutput failing: UnrecoverableKeyException: Rejected by the jceks.key.serialFilter or jdk.serialFilter property

stack created HBASE-20538: - Summary: TestSaslFanOutOneBlockAsyncDFSOutput failing: UnrecoverableKeyException: Rejected by the jceks.key.serialFilter or jdk.serialFilter property Key: HBASE-20538 URL:

Re: On the 2.1.0 and 3.0.0 release

>We disabled it by default in the end due to some performance issues... Thanks for the info. I missed the party. :( On 2018/05/07 06:41:51, 张铎(Duo Zhang) wrote: > 2018-05-07 14:38 GMT+08:00 Chia-Ping Tsai : > > > > As I volunteered to be the release

[jira] [Created] (HBASE-20537) The download link is not available in the downloads webpage

Ismaël Mejía created HBASE-20537: Summary: The download link is not available in the downloads webpage Key: HBASE-20537 URL: https://issues.apache.org/jira/browse/HBASE-20537 Project: HBase

Re: On the 2.1.0 and 3.0.0 release

bq. As I volunteered to be the release manager for the 2.1 release line I guess we could expect another great release line (smile) bq. For the 2.1 release line... I could see more "Punted out of 2.0" features in our 2.0 doc

[jira] [Created] (HBASE-20536) Make TestRegionServerAccounting stable and it should not use absolute number

Guanghao Zhang created HBASE-20536: -- Summary: Make TestRegionServerAccounting stable and it should not use absolute number Key: HBASE-20536 URL: https://issues.apache.org/jira/browse/HBASE-20536

Re: On the 2.1.0 and 3.0.0 release

Let's do big features in 3.0.0 only. Ideally there will no big new features for a minor release, so that we can move the stable pointer to newer minor versions quickly and retire the old branches. It will be a nightmare if we have lots of active minor release lines... 2018-05-07 14:53 GMT+08:00

Re: On the 2.1.0 and 3.0.0 release

Why 2.1 doesn't contatin synchronous replication? This can be a experiment feature in 2.1? 2018-05-07 14:41 GMT+08:00 张铎(Duo Zhang) : > 2018-05-07 14:38 GMT+08:00 Chia-Ping Tsai : > > > > As I volunteered to be the release manager for the 2.1 release

Re: On the 2.1.0 and 3.0.0 release

2018-05-07 14:38 GMT+08:00 Chia-Ping Tsai : > > As I volunteered to be the release manager for the 2.1 release line so > let > > me bring this up. > +1 to Duo be RM of 2.1 release. > > > disabled from 2.0.0 release, for example, serial replication, and in > memory compaction

Re: On the 2.1.0 and 3.0.0 release

> As I volunteered to be the release manager for the 2.1 release line so let > me bring this up. +1 to Duo be RM of 2.1 release. > disabled from 2.0.0 release, for example, serial replication, and in memory > compaction IIRC, in memory compaction is enabled in 2.0 and the default policy is