[jira] [Created] (HBASE-20321) Review of MobFileCache Class

BELUGA BEHR created HBASE-20321: --- Summary: Review of MobFileCache Class Key: HBASE-20321 URL: https://issues.apache.org/jira/browse/HBASE-20321 Project: HBase Issue Type: Improvement

Re: building hbase with native libraries

Agreed. Always best to build both Hadoop and HBase from source, specifying the right version on the Maven command line as you do, and then take the extra step to (re)package with native libs included. On Thu, Mar 29, 2018 at 3:21 PM, rahul gidwani wrote: > Hi Andrew, >

Re: building hbase with native libraries

Hi Andrew, I was thinking about doing the same thing as you are doing now. It seems like the safest approach, this will allow us to upgrade our hadoop binaries independent of having to worry about doing anything with hbase. I think this should be the recommended approach in building hbase as

[jira] [Created] (HBASE-20320) Review of MemcachedBlockCache

BELUGA BEHR created HBASE-20320: --- Summary: Review of MemcachedBlockCache Key: HBASE-20320 URL: https://issues.apache.org/jira/browse/HBASE-20320 Project: HBase Issue Type: Improvement

[jira] [Resolved] (HBASE-20318) Lower "Set storagePolicy=XXX for path=YYY" INFO level logging to DEBUG

[ https://issues.apache.org/jira/browse/HBASE-20318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-20318. Resolution: Invalid Fix Version/s: (was: 2.0.1) (was:

[jira] [Resolved] (HBASE-20132) Change the "KV" to "Cell" for web UI

[ https://issues.apache.org/jira/browse/HBASE-20132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-20132. --- Resolution: Fixed Pushed to branch-2.0. Thanks for the patch [~andrewcheng] and for guidance [~chia7712] >

[jira] [Reopened] (HBASE-20132) Change the "KV" to "Cell" for web UI

[ https://issues.apache.org/jira/browse/HBASE-20132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reopened HBASE-20132: --- Reopened to backport to branch-2.0. > Change the "KV" to "Cell" for web UI >

Re: building hbase with native libraries

FWIW, I build Hadoop and HBase binary tarballs. As a post build step, I extract lib/native/ from the Hadoop tarball, extract the HBase tarball, copy Hadoop's lib/native/ to HBase's lib/native/ e.g. cp -a hadoop-2.7.5/lib/native hbase-1.4.2/lib/native/Linux-amd64-64 (you can learn your

Re: [DISCUSS] purge the 'component owner' experiment?

It was an interesting experiment but we had more active committers at that time. Now the would-be owners are more likely to be a bottleneck (due to limited bandwidth for review) than an aid. On Wed, Mar 28, 2018 at 7:42 AM, Sean Busbey wrote: > In late 2012 we tried an

[jira] [Created] (HBASE-20319) Run a check that branch-2.0 has all it needs from branch-2

stack created HBASE-20319: - Summary: Run a check that branch-2.0 has all it needs from branch-2 Key: HBASE-20319 URL: https://issues.apache.org/jira/browse/HBASE-20319 Project: HBase Issue Type:

[jira] [Created] (HBASE-20318) Lower "Set storagePolicy=XXX for path=YYY" INFO level logging to DEBUG

Andrew Purtell created HBASE-20318: -- Summary: Lower "Set storagePolicy=XXX for path=YYY" INFO level logging to DEBUG Key: HBASE-20318 URL: https://issues.apache.org/jira/browse/HBASE-20318 Project:

[jira] [Created] (HBASE-20317) Backport HBASE-20261 "Table page (table.jsp) in Master UI does not show replicaIds for hbase meta table" to branch-1

stack created HBASE-20317: - Summary: Backport HBASE-20261 "Table page (table.jsp) in Master UI does not show replicaIds for hbase meta table" to branch-1 Key: HBASE-20317 URL:

[jira] [Created] (HBASE-20316) Backport HBASE-20229 "ConnectionImplementation.locateRegions() returns duplicated entries when region replication is on" to branch-1

stack created HBASE-20316: - Summary: Backport HBASE-20229 "ConnectionImplementation.locateRegions() returns duplicated entries when region replication is on" to branch-1 Key: HBASE-20316 URL:

[jira] [Created] (HBASE-20315) Document post release process steps for RM

Andrew Purtell created HBASE-20315: -- Summary: Document post release process steps for RM Key: HBASE-20315 URL: https://issues.apache.org/jira/browse/HBASE-20315 Project: HBase Issue Type:

Re: Exclude H0 from the pre commit build machines

Filed HBASE-20314. 2018-03-29 22:21 GMT+08:00 Sean Busbey : > please make sure there's a jira tracking the strange error so that I > can dig into it later. > > On Thu, Mar 29, 2018 at 9:19 AM, 张铎(Duo Zhang) > wrote: > > It seems that all builds on H0

[jira] [Created] (HBASE-20314) Pre commit build for master branch fails

Duo Zhang created HBASE-20314: - Summary: Pre commit build for master branch fails Key: HBASE-20314 URL: https://issues.apache.org/jira/browse/HBASE-20314 Project: HBase Issue Type: Bug

Re: Exclude H0 from the pre commit build machines

Seems not related to the build machine, it also failed on H15 just now. And seems the problem only happens for master branch, for branch-1 it works well https://builds.apache.org/job/PreCommit-HBASE-Build/12205/ 2018-03-29 22:21 GMT+08:00 Sean Busbey : > please make sure

Re: [ANNOUNCE] Apache HBase Thirdparty 2.1.0 released

I can't find anything written down; but I just did a couple of simple mail searches. Probably this should build on HBASE-15317. How about I try to incorporate a note about it when implementing there and you can keep me honest with a review? On Thu, Mar 29, 2018 at 9:24 AM, Josh Elser

Re: [ANNOUNCE] Apache HBase Thirdparty 2.1.0 released

Welp, the announce message got bounced anyways, so it didn't actually go out. Is this written down somewhere that I missed? I was just going off of the standard ASF-release knowledge I have floating around. If not, should I add it to the book somewhere? Thanks Sean. On 3/28/18 8:12 PM,

Re: Exclude H0 from the pre commit build machines

please make sure there's a jira tracking the strange error so that I can dig into it later. On Thu, Mar 29, 2018 at 9:19 AM, 张铎(Duo Zhang) wrote: > It seems that all builds on H0 have failed with strange error. Exclude it > from the build machines to see if it could help.

Exclude H0 from the pre commit build machines

It seems that all builds on H0 have failed with strange error. Exclude it from the build machines to see if it could help.

[jira] [Created] (HBASE-20313) Canary documentation is incorrect in reference guide

Peter Somogyi created HBASE-20313: - Summary: Canary documentation is incorrect in reference guide Key: HBASE-20313 URL: https://issues.apache.org/jira/browse/HBASE-20313 Project: HBase Issue

[jira] [Created] (HBASE-20312) CCSMap: A faster, GC-friendly, less memory Concurrent Map for memstore

Xiang Wang created HBASE-20312: -- Summary: CCSMap: A faster, GC-friendly, less memory Concurrent Map for memstore Key: HBASE-20312 URL: https://issues.apache.org/jira/browse/HBASE-20312 Project: HBase

Re: [jira] [Created] (HBASE-20303) RS RPC server should not allow the response queue size to be too large

UNSUBSCRIBE On Wed, Mar 28, 2018 at 7:31 PM, Chance Li (JIRA) wrote: > Chance Li created HBASE-20303: > - > > Summary: RS RPC server should not allow the response queue > size to be too large > Key: HBASE-20303 >

Can we support seek for a reverse scan?

Hi folks, We are facing “IllegalStateException: requestSeek cannot be called on ReversedKeyValueHeap" when using a reverse scan and the loadColumnFamiliesOnDemand optimization is enabled. As ReversedKeyValueHeap doesn't support requestSeek, it seems like the IllegalStateException occurs. I