[jira] [Created] (HBASE-18626) Handle the incompatible change about the replication TableCFs' config

Guanghao Zhang created HBASE-18626: -- Summary: Handle the incompatible change about the replication TableCFs' config Key: HBASE-18626 URL: https://issues.apache.org/jira/browse/HBASE-18626 Project:

[jira] [Resolved] (HBASE-9417) SecureBulkLoadEndpoint should be folded in core

[ https://issues.apache.org/jira/browse/HBASE-9417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He resolved HBASE-9417. - Resolution: Duplicate Fix Version/s: (was: 2.0.0-alpha-3) > SecureBulkLoadEndpoint should be

[jira] [Created] (HBASE-18625) Splitting of region with replica, doesn't update region list in serverHolding.

He Fei created HBASE-18625: -- Summary: Splitting of region with replica, doesn't update region list in serverHolding. Key: HBASE-18625 URL: https://issues.apache.org/jira/browse/HBASE-18625 Project: HBase

[jira] [Resolved] (HBASE-18489) Expose scan cursor in RawScanResultConsumer

[ https://issues.apache.org/jira/browse/HBASE-18489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-18489. --- Resolution: Fixed Pushed the addendum to master and branch-2. > Expose scan cursor in

[jira] [Reopened] (HBASE-18489) Expose scan cursor in RawScanResultConsumer

[ https://issues.apache.org/jira/browse/HBASE-18489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-18489: --- Revert some unnecessary changes... > Expose scan cursor in RawScanResultConsumer >

[jira] [Created] (HBASE-18624) Added support for clearing BlockCache

Ajay Jadhav created HBASE-18624: --- Summary: Added support for clearing BlockCache Key: HBASE-18624 URL: https://issues.apache.org/jira/browse/HBASE-18624 Project: HBase Issue Type: Improvement

Re: [DISCUSS] Should L2 cache be strictly L2 by default

Yes I would also say the current way is better. Specially after the off heap read path improve, we are at almost same perf from bucket cache compared to LRU cache. So it would be better to work with a small Java heap and small L1 cache size. (This is not strict L1 vs L2 . Still I call it that

[jira] [Created] (HBASE-18623) Frequent failed to parse at EOF warnings from WALEntryStream

Andrew Purtell created HBASE-18623: -- Summary: Frequent failed to parse at EOF warnings from WALEntryStream Key: HBASE-18623 URL: https://issues.apache.org/jira/browse/HBASE-18623 Project: HBase

Re: Moving 2.0 forward

On Thu, Aug 17, 2017 at 12:45 PM, Mike Drob wrote: > I went ahead and tagged those as tentatively 2.0.0-alpha3 in jira so that > we can have them all in one place later. Folks can move additional issues > in and out as they see appropriate. > > Thanks M, S > On Thu, Aug 17,

Re: Moving 2.0 forward

I went ahead and tagged those as tentatively 2.0.0-alpha3 in jira so that we can have them all in one place later. Folks can move additional issues in and out as they see appropriate. On Thu, Aug 17, 2017 at 2:35 PM, Stack wrote: > I put up the hbase-2.0.0-alpha2 release

Re: [DISCUSS] Should L2 cache be strictly L2 by default

Some more info, when COMBINED=false, this is what happens: // L1 and L2 are not 'combined'. They are connected via the LruBlockCache victimhandler // mechanism. It is a little ugly but works according to the following: when the // background eviction thread runs, blocks evicted from L1 will go to

Re: Moving 2.0 forward

I put up the hbase-2.0.0-alpha2 release candidate. Please vote on it. For hbase-2.0.0-alpha3, the theme is solidifying API. I hope to get a release out in the next week or so. I did a weeding of 2.0.0 issues over the last day. If folks are interested in helping out, below are the items I think

[jira] [Created] (HBASE-18622) Mitigate compatibility concerns between branch-1 and branch-2

stack created HBASE-18622: - Summary: Mitigate compatibility concerns between branch-1 and branch-2 Key: HBASE-18622 URL: https://issues.apache.org/jira/browse/HBASE-18622 Project: HBase Issue Type:

Re: [DISCUSS] Jira Gardening - HBASE-12259

No objections == lazy consensus. Issues have been resolved as "won't fix" - somebody please reopen them if I made an error. On Mon, Aug 14, 2017 at 12:59 PM, Stack wrote: > +1 on closing issues that have not seen movement in years. > S > > On Mon, Aug 14, 2017 at 8:09 AM, Mike

[DISCUSS] Should L2 cache be strictly L2 by default

Currently BUCKET_CACHE_COMBINED_KEY is set to "true" by default [1] which makes L2 cache not strictly L2 cache. From the usability perspective, it is better to set BUCKET_CACHE_COMBINED_KEY to "false" so that L2 cache would behave strictly L2 and also use the L1 cache to store data blocks

Re: [VOTE] First hbase-2.0.0-alpha-2 Release Candidate is available

+1 from me. St.Ack On Wed, Aug 16, 2017 at 1:43 PM, Stack wrote: > The first release candidate for HBase 2.0.0-alpha-2 is up at: > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-2RC0/ > > Maven artifacts are available from a staging directory here: > >

Re: Moving 2.0 forward

On Wed, Aug 16, 2017 at 10:18 PM, Guanghao Zhang wrote: > About compatibility, there is one incompatible change about the replication > TableCFs' config. The old config is a string and it concatenate the list of > tables and column families in format

[jira] [Created] (HBASE-18621) Refactor ClusterOptions before applying to code base

Reid Chan created HBASE-18621: - Summary: Refactor ClusterOptions before applying to code base Key: HBASE-18621 URL: https://issues.apache.org/jira/browse/HBASE-18621 Project: HBase Issue Type:

[jira] [Created] (HBASE-18620) Secure bulkload job fails when HDFS umask has limited scope

Pankaj Kumar created HBASE-18620: Summary: Secure bulkload job fails when HDFS umask has limited scope Key: HBASE-18620 URL: https://issues.apache.org/jira/browse/HBASE-18620 Project: HBase

[jira] [Created] (HBASE-18619) Should we add a postOpenDeployTasks after open splited or merged region?

Jingyun Tian created HBASE-18619: Summary: Should we add a postOpenDeployTasks after open splited or merged region? Key: HBASE-18619 URL: https://issues.apache.org/jira/browse/HBASE-18619 Project:

[jira] [Created] (HBASE-18618) Backport HBASE-16729 (Define the behavior of (default) empty FilterList) to branch-1

Pankaj Kumar created HBASE-18618: Summary: Backport HBASE-16729 (Define the behavior of (default) empty FilterList) to branch-1 Key: HBASE-18618 URL: https://issues.apache.org/jira/browse/HBASE-18618