Re: Moving 2.0 forward

2017-12-13 Thread Stack
Update. See below. On Tue, Dec 5, 2017 at 10:43 AM, Stack wrote: > Update on hbase-2.0.0-beta-1. I'm going to put up a beta-1 RC before > Christmas day. > > Still aiming for an hbase2 beta-1 showing up in your christmas stocking. > Here is the list [1]. We're doing pretty

[jira] [Resolved] (HBASE-18978) Align the methods in Table and AsyncTable

2017-12-13 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-18978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-18978. --- Resolution: Fixed Hadoop Flags: Reviewed Ok. Resolving this effort for now. We may be back but it will

[jira] [Created] (HBASE-19511) Splits causes blocks to be cached again and so such blocks cannot be evicted from bucket cache

2017-12-13 Thread ramkrishna.s.vasudevan (JIRA)
ramkrishna.s.vasudevan created HBASE-19511: -- Summary: Splits causes blocks to be cached again and so such blocks cannot be evicted from bucket cache Key: HBASE-19511 URL:

Re: [VOTE] The second HBase 1.4.0 release candidate (RC1) is available

2017-12-13 Thread Andrew Purtell
And here are results for PE. https://bigdatasf.s3.amazonaws.com/assets/pe_1.2.6_1.4.0RC1.png https://bigdatasf.s3.amazonaws.com/assets/pe_1.2.6_1.4.0RC1.xlsx [image: Inline image 1] Similar to the YCSB results, 1.2.6 and 1.4.0 RC1 are close, but 1.4.0 RC1 shows superior results. Cluster: 1

[jira] [Created] (HBASE-19510) TestDistributedLogSplitting is flakey for AsyncFSWAL

2017-12-13 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-19510: - Summary: TestDistributedLogSplitting is flakey for AsyncFSWAL Key: HBASE-19510 URL: https://issues.apache.org/jira/browse/HBASE-19510 Project: HBase Issue Type:

[ANNOUNCE] Apache HBase 1.1.13 is now available for download

2017-12-13 Thread Nick Dimiduk
The HBase team is happy to announce the immediate availability of HBase 1.1.13! Download it from an Apache mirror near you, http://www.apache.org/dyn/closer.lua/hbase/, or wire up through the maven repo. Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase

Re: [VOTE] The second HBase 1.4.0 release candidate (RC1) is available

2017-12-13 Thread Andrew Purtell
For those who voted on RC0, are you willing to transfer your vote to RC1? If so, please cast it. There were 5 changes in RC1 not in RC0. See below for the list. On Fri, Dec 8, 2017 at 5:50 PM, Andrew Purtell wrote: > The second HBase 1.4.0​ release candidate (RC1) is

[jira] [Created] (HBASE-19509) RSGroupAdminEndpoint#preCreateTable triggers TableNotFoundException

2017-12-13 Thread Ted Yu (JIRA)
Ted Yu created HBASE-19509: -- Summary: RSGroupAdminEndpoint#preCreateTable triggers TableNotFoundException Key: HBASE-19509 URL: https://issues.apache.org/jira/browse/HBASE-19509 Project: HBase

[jira] [Resolved] (HBASE-19212) Align coprocessor in Table and AsyncTable

2017-12-13 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-19212. --- Resolution: Later One invocation is async and the other sync. The way you call CP is different in Table and

Re: Moving To SLF4J and Log4J2

2017-12-13 Thread Stack
On Mon, Dec 11, 2017 at 12:49 PM, Apekshit Sharma wrote: > Seems like good idea: > - remove long dead dependency > - a bit cleaner code > - hadoop also moved to slf4j > > Quickly looking at codebase to get idea of amount of work required, here > are some numbers: > - LOG.debug

Re: Can we always add new regions as CLOSED?

2017-12-13 Thread Stack
On Wed, Dec 13, 2017 at 1:14 AM, Apekshit Sharma wrote: > Hi folks, > > Was debugging TestTruncateTableProcedure when starting thinking about this. > (That's one mean test! What nice fault tolerant tests!) > > So the specific case: If we fail after adding new regions to meta (

[jira] [Created] (HBASE-19508) ReadOnlyConfiguration throws exception if any Configuration in current context calls addDefautlResource

2017-12-13 Thread stack (JIRA)
stack created HBASE-19508: - Summary: ReadOnlyConfiguration throws exception if any Configuration in current context calls addDefautlResource Key: HBASE-19508 URL: https://issues.apache.org/jira/browse/HBASE-19508

[jira] [Reopened] (HBASE-19484) The value array written by ExtendedCell#write is out of bounds

2017-12-13 Thread Chia-Ping Tsai (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai reopened HBASE-19484: getValueArray() can return null so we should add the length check before writing the value

[jira] [Created] (HBASE-19507) get Mob by rowkey only return error value when run compact_mob or major_compact_mob after change MOB_THRESHOLD

2017-12-13 Thread WangYuan (JIRA)
WangYuan created HBASE-19507: Summary: get Mob by rowkey only return error value when run compact_mob or major_compact_mob after change MOB_THRESHOLD Key: HBASE-19507 URL:

[jira] [Created] (HBASE-19506) Support variable sized chunks from ChunkCreator

2017-12-13 Thread Anastasia Braginsky (JIRA)
Anastasia Braginsky created HBASE-19506: --- Summary: Support variable sized chunks from ChunkCreator Key: HBASE-19506 URL: https://issues.apache.org/jira/browse/HBASE-19506 Project: HBase

[jira] [Created] (HBASE-19505) Disable ByteBufferPool by default at HM

2017-12-13 Thread Anoop Sam John (JIRA)
Anoop Sam John created HBASE-19505: -- Summary: Disable ByteBufferPool by default at HM Key: HBASE-19505 URL: https://issues.apache.org/jira/browse/HBASE-19505 Project: HBase Issue Type:

Can we always add new regions as CLOSED?

2017-12-13 Thread Apekshit Sharma
Hi folks, Was debugging TestTruncateTableProcedure when starting thinking about this. (That's one mean test! What nice fault tolerant tests!) So the specific case: If we fail after adding new regions to meta ( TRUNCATE_TABLE_ADD_TO_META