[jira] [Created] (HBASE-19563) A few hbase-procedure classes missing @InterfaceAudience annotation

Guanghao Zhang created HBASE-19563: -- Summary: A few hbase-procedure classes missing @InterfaceAudience annotation Key: HBASE-19563 URL: https://issues.apache.org/jira/browse/HBASE-19563 Project:

[jira] [Created] (HBASE-19562) Purge mirror writing of region and table info into fs at .tableinfo and .regioninfo

stack created HBASE-19562: - Summary: Purge mirror writing of region and table info into fs at .tableinfo and .regioninfo Key: HBASE-19562 URL: https://issues.apache.org/jira/browse/HBASE-19562 Project: HBase

Re: Cleanup and remove the code path where is no hbase.client.rpc.codec

AbstractTestIPC is a good test. And it will continue to work after this proposed change, because we still want the server to be able to handle no codec (and pb) case, for backward compatibility. The proposal is to remove the support of no codec from the RpcClient at the moment. There will always

Re: Cleanup and remove the code path where is no hbase.client.rpc.codec

So the proposal is to avoid the empty config and have a better defined config if we need No pb way? Ya I agree to it if this empty way seems odd to config. Any non - java client what will be the value for this config? Regards Ram On Wed, Dec 20, 2017 at 8:40 AM, 张铎(Duo Zhang)

Re: [DISCUSSION] Default configurations in hbase-2.0.0 hbase-default.xml

Is there an option with a pure Java fallback if the native codec isn't available? I mean something reasonable, not bzip2. > On Dec 19, 2017, at 6:16 PM, Dave Latham wrote: > > What about LZ4 instead? Most benchmarks I've seen show it ahead of Snappy. > >> On Tue, Dec

[jira] [Created] (HBASE-19561) maxCacheSize in CacheEvictionStats can't be accumulated repeatedly When dealing with each region

Guangxu Cheng created HBASE-19561: - Summary: maxCacheSize in CacheEvictionStats can't be accumulated repeatedly When dealing with each region Key: HBASE-19561 URL:

[jira] [Created] (HBASE-19560) create make-rc.sh for hbase-thirdparty

Mike Drob created HBASE-19560: - Summary: create make-rc.sh for hbase-thirdparty Key: HBASE-19560 URL: https://issues.apache.org/jira/browse/HBASE-19560 Project: HBase Issue Type: Task

Re: Cleanup and remove the code path where is no hbase.client.rpc.codec

See AbstractTestIPC, there is a testNoCodec. But I agree that we should have a default fallback codec always. 2017-12-20 11:02 GMT+08:00 Jerry He : > RPC_CODEC_CONF_KEY 'hbase.client.rpc.codec' is a property we use on the > client side to determine the RPC codec. > > It

Cleanup and remove the code path where is no hbase.client.rpc.codec

RPC_CODEC_CONF_KEY 'hbase.client.rpc.codec' is a property we use on the client side to determine the RPC codec. It currently has a strange logic. Whereas the default is KeyValueCodec, we allow a user to specify an empty string "" as the a way to indicate there is no codec class and we should not

Re: [DISCUSSION] Default configurations in hbase-2.0.0 hbase-default.xml

https://community.cloudera.com/t5/Hadoop-101-Training-Quickstart/LZO-LZ4-SNAPPY-which-is-the-fastest-compression-codec/td-p/49338 This link may explain to choose which. I think mike's idea work, if snappy is not available, just fall back to another compression-codec, or no compression.

[jira] [Created] (HBASE-19559) Fix TestLogRolling.testLogRollOnDatanodeDeath

Duo Zhang created HBASE-19559: - Summary: Fix TestLogRolling.testLogRollOnDatanodeDeath Key: HBASE-19559 URL: https://issues.apache.org/jira/browse/HBASE-19559 Project: HBase Issue Type: Bug

Re: [DISCUSSION] Default configurations in hbase-2.0.0 hbase-default.xml

What about LZ4 instead? Most benchmarks I've seen show it ahead of Snappy. On Tue, Dec 19, 2017 at 5:55 PM, Mike Drob wrote: > Can you file a JIRA for some kind of magical default snappy-if-available? > > On Tue, Dec 19, 2017 at 7:38 PM, Stack wrote: > > >

[jira] [Resolved] (HBASE-18429) ITs attempt to modify immutable table/column descriptors

[ https://issues.apache.org/jira/browse/HBASE-18429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-18429. Resolution: Fixed Assignee: Mike Drob Resolve this as all sub-tasks done. > ITs

Re: [DISCUSSION] Default configurations in hbase-2.0.0 hbase-default.xml

Can you file a JIRA for some kind of magical default snappy-if-available? On Tue, Dec 19, 2017 at 7:38 PM, Stack wrote: > On Tue, Dec 19, 2017 at 4:22 PM, Stack wrote: > > > Thanks for jumping in JMS. Ok on the by-table. > > > > SNAPPY license seems fine.

Re: [DISCUSSION] Default configurations in hbase-2.0.0 hbase-default.xml

On Tue, Dec 19, 2017 at 4:22 PM, Stack wrote: > Thanks for jumping in JMS. Ok on the by-table. > > SNAPPY license seems fine. We'd enable it as default when you create a > table? Let me play w/ it. > > Oh. I forgot what happens if the native lib is not available, how cluster

Re: [DISCUSSION] Default configurations in hbase-2.0.0 hbase-default.xml

Thanks for jumping in JMS. Ok on the by-table. SNAPPY license seems fine. We'd enable it as default when you create a table? Let me play w/ it. Anything else from your experience that we should change JMS? Thanks sir, S On Tue, Dec 19, 2017 at 1:47 PM, Jean-Marc Spaggiari <

[jira] [Resolved] (HBASE-19558) TestRegionsOnMasterOptions hack so it works reliablly

[ https://issues.apache.org/jira/browse/HBASE-19558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-19558. --- Resolution: Fixed I pushed the below which just waits until there are not RIT before it calls cluster

[jira] [Created] (HBASE-19558) TestRegionsOnMasterOptions hack so it works reliablly

stack created HBASE-19558: - Summary: TestRegionsOnMasterOptions hack so it works reliablly Key: HBASE-19558 URL: https://issues.apache.org/jira/browse/HBASE-19558 Project: HBase Issue Type: Bug

Re: [DISCUSS] Release timetable for the 1.4 code line

Sounds good to me Andy, St.Ack On Tue, Dec 19, 2017 at 11:53 AM, Andrew Purtell wrote: > Greetings HBasers, > > I would like to propose a release timetable for the 1.4 code line as > follows. The below would be what we commit to: > >- December 2017: 1.4.0 >​ ​ >

[jira] [Created] (HBASE-19557) Build and release source jars for hbase-shaded-client and others

Jerry He created HBASE-19557: Summary: Build and release source jars for hbase-shaded-client and others Key: HBASE-19557 URL: https://issues.apache.org/jira/browse/HBASE-19557 Project: HBase

Re: [VOTE] hbase-thirdparty 2.0.0 RC

Undoing the tarball in a dir empty but for the tgz looks like this: drwxr-xr-x 3 stack staff102 Dec 19 09:23 src -rw-r--r-- 1 stack staff 13487 Dec 19 09:23 pom.xml drwxr-xr-x 4 stack staff136 Dec 19 09:23 hbase-shaded-protobuf drwxr-xr-x 3 stack staff102 Dec 19 09:23

Re: [DISCUSS] Release timetable for the 1.4 code line

Maybe we can stagger the work by half months? I'd like to give the 2.0 candidates as much time as my own 1.x ones, so it is definitely a consideration I will keep in mind. > On Dec 19, 2017, at 12:40 PM, Mike Drob wrote: > > In theory, this sounds good to me. > > Where

[jira] [Resolved] (HBASE-19171) Update package references to match new shaded offset in hbase-thirdparty

[ https://issues.apache.org/jira/browse/HBASE-19171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He resolved HBASE-19171. -- Resolution: Duplicate Fix Version/s: (was: 2.0.0-beta-1) Resolve as dup of the other task

Re: [DISCUSSION] Default configurations in hbase-2.0.0 hbase-default.xml

Can we get all tables by default Snappy compressed? I think because of the license we can not, right? Just asking, in case there is an option for that... Also +1 on balancing by table... 2017-12-18 17:34 GMT-05:00 Stack : > (I thought I'd already posted a DISCUSSION on defaults

[VOTE] hbase-thirdparty 2.0.0 RC

HBase Devs, In preparation for our hbase-2.0.0-beta releases, it would be beneficial to have updated third-party artifacts. These artifacts update the version of netty to 4.1.17 (from 4.1.12) and change the relocation offset to o.a.h.thirdparty to prevent conflicts with our other shaded

Re: [DISCUSS] Release timetable for the 1.4 code line

In theory, this sounds good to me. Where practical, let's make sure to coordinate with the 2.0 efforts so that we don't overburden our testers or end up with multiple release votes in too quick succession. I don't expect this to happen because all of our release managers are gracious individuals,

[jira] [Resolved] (HBASE-18684) [hbase-thirdparty] Remove CHANGES, update NOTICES

[ https://issues.apache.org/jira/browse/HBASE-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-18684. --- Resolution: Fixed > [hbase-thirdparty] Remove CHANGES, update NOTICES >

[DISCUSS] Release timetable for the 1.4 code line

Greetings HBasers, I would like to propose a release timetable for the 1.4 code line as follows. The below would be what we commit to: - December 2017: 1.4.0 ​ ​ - Now released!​ - January 2018 ​: 1.4.1​ - ​Sweep up changes missed at the 1.4.0 cutoff, especially ​ ​​

[ANNOUNCE] Apache HBase 1.4.0 is now available for download

The HBase team is happy to announce the immediate availability of Apache ​HBase​ 1.4.0! 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] [Created] (HBASE-19556) Remove TestAssignmentManager#testGoodSplit, which no longer make sense

Yi Liang created HBASE-19556: Summary: Remove TestAssignmentManager#testGoodSplit, which no longer make sense Key: HBASE-19556 URL: https://issues.apache.org/jira/browse/HBASE-19556 Project: HBase

Re: Moving To SLF4J and Log4J2

On Tue, Dec 19, 2017 at 7:29 AM, Balazs Meszaros < balazs.mesza...@cloudera.com> wrote: > Thanks for reviewing Appy! > > 1. I tried to verify it, log level changes take place through the web ui. > 2. I put back fatals. > 3. The property files are still compatible, because I have not updated >

[jira] [Resolved] (HBASE-18855) rewrite netty so to have proper packages

[ https://issues.apache.org/jira/browse/HBASE-18855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-18855. --- Resolution: Not A Problem Starting with netty 4.1.14, it seems like they fixed enough internals that

Re: Major Compaction Tool

thanks for all the great feedback! I opened a ticket here: https://issues.apache.org/jira/browse/HBASE-19528 Lets continue the discussion there. On Fri, Dec 15, 2017 at 11:34 PM, sahil aggarwal wrote: > Hi, > > We wrote something similar. It just triggers major

[jira] [Resolved] (HBASE-19548) Backport the missed doc fix from master to branch-2

[ https://issues.apache.org/jira/browse/HBASE-19548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved HBASE-19548. Resolution: Fixed Assignee: Chien Hsiang Tang (was: Chia-Ping Tsai) Fix

Re: Moving To SLF4J and Log4J2

I remember doing the research for this many moons ago on a different project, and dynamically setting log levels (like we do via web ui) is simply not supported in slf4j. On Tue, Dec 19, 2017 at 9:29 AM, Balazs Meszaros < balazs.mesza...@cloudera.com> wrote: > Thanks for reviewing Appy! > > 1. I

Re: Moving To SLF4J and Log4J2

Thanks for reviewing Appy! 1. I tried to verify it, log level changes take place through the web ui. 2. I put back fatals. 3. The property files are still compatible, because I have not updated log4j to log4j2 yet. But they won't be compatible after the update. 4. I also updated those projects.

[jira] [Created] (HBASE-19555) TestSplitTransactionOnCluster is flaky

Peter Somogyi created HBASE-19555: - Summary: TestSplitTransactionOnCluster is flaky Key: HBASE-19555 URL: https://issues.apache.org/jira/browse/HBASE-19555 Project: HBase Issue Type: Bug

[jira] [Created] (HBASE-19554) AbstractTestDLS.testThreeRSAbort sometimes fails in pre commit

Duo Zhang created HBASE-19554: - Summary: AbstractTestDLS.testThreeRSAbort sometimes fails in pre commit Key: HBASE-19554 URL: https://issues.apache.org/jira/browse/HBASE-19554 Project: HBase