[jira] [Resolved] (HBASE-19153) LruBlockCache cache too big blocks logic error

[ https://issues.apache.org/jira/browse/HBASE-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhang Quanjin resolved HBASE-19153. --- Resolution: Not A Bug > LruBlockCache cache too big blocks logic error >

[jira] [Created] (HBASE-19166) Add translation for handling hbase.regionserver.wal.WALEdit

Ted Yu created HBASE-19166: -- Summary: Add translation for handling hbase.regionserver.wal.WALEdit Key: HBASE-19166 URL: https://issues.apache.org/jira/browse/HBASE-19166 Project: HBase Issue Type:

Re: [DISCUSS] shading hbase-client jackson dependency

jackson-databind and anything that depends on, maybe. I think we should figure out the situation with hbase-shaded-testing-util first, then I can unwind the rest of the tree. On Thu, Nov 2, 2017 at 5:46 PM, Stack wrote: > On Wed, Nov 1, 2017 at 10:58 AM, Mike Drob

Re: [DISCUSS] shading hbase-client jackson dependency

On Wed, Nov 1, 2017 at 10:58 AM, Mike Drob wrote: > Hi Devs, > > Should have thought to discuss this sooner, but I had blinders on at the > time and wasn't thinking about the bigger picture. > > Currently, hbase-client carries with it a dependency on jackson due to our >

[jira] [Created] (HBASE-19165) TODO Handle stuck in transition: rit=OPENING, location=ve0538....

stack created HBASE-19165: - Summary: TODO Handle stuck in transition: rit=OPENING, location=ve0538 Key: HBASE-19165 URL: https://issues.apache.org/jira/browse/HBASE-19165 Project: HBase Issue

Re: Problem with double shading in hbase-thirdparty and hbase-shaded-client?

o.a.h.hbase.thirdparty does look like a better choice. Let me open two JIRAs to change the hbase-thirdparty and then all the references in the main code (more tedious part). Thanks, guys! On Thu, Nov 2, 2017 at 1:54 PM Sean Busbey wrote: > I think something like

[jira] [Created] (HBASE-19164) Avoid UUID.randomUUID in tests

Mike Drob created HBASE-19164: - Summary: Avoid UUID.randomUUID in tests Key: HBASE-19164 URL: https://issues.apache.org/jira/browse/HBASE-19164 Project: HBase Issue Type: Bug

[jira] [Created] (HBASE-19163) "Maximum Lock Acquired" from region server's batch processing

huaxiang sun created HBASE-19163: Summary: "Maximum Lock Acquired" from region server's batch processing Key: HBASE-19163 URL: https://issues.apache.org/jira/browse/HBASE-19163 Project: HBase

[jira] [Created] (HBASE-19162) bin/hbase cli help should be more forthcoming

Sean Busbey created HBASE-19162: --- Summary: bin/hbase cli help should be more forthcoming Key: HBASE-19162 URL: https://issues.apache.org/jira/browse/HBASE-19162 Project: HBase Issue Type:

[jira] [Created] (HBASE-19161) If config 'hbase.systemtables.compacting.memstore.type' is not specified then DefaultMemStore is used

Umesh Agashe created HBASE-19161: Summary: If config 'hbase.systemtables.compacting.memstore.type' is not specified then DefaultMemStore is used Key: HBASE-19161 URL:

Re: Problem with double shading in hbase-thirdparty and hbase-shaded-client?

I think something like o.a.h.hbase.thirdparty might be better. then we can differentiate between "shaded" for downstream of us vs "thirdparty" for our internal use. On Thu, Nov 2, 2017 at 3:52 PM, Stack wrote: > Good one Jerry He. > > I can try changing the offset in

Re: Problem with double shading in hbase-thirdparty and hbase-shaded-client?

Good one Jerry He. I can try changing the offset in hbase-thirdparty in a new release (o.a.hbase.shaded?). There used to be a reason why it had to be o.a.h.hbase.shaded but IIRC it went away after all shaded dependencies made it out to hbase-thirdparty (including the pb3 that we used to have

[jira] [Created] (HBASE-19160) Re-expose some CellUtil methods

Mike Drob created HBASE-19160: - Summary: Re-expose some CellUtil methods Key: HBASE-19160 URL: https://issues.apache.org/jira/browse/HBASE-19160 Project: HBase Issue Type: Bug Affects

[jira] [Created] (HBASE-19159) Backup should check permission for snapshot copy in advance

Ted Yu created HBASE-19159: -- Summary: Backup should check permission for snapshot copy in advance Key: HBASE-19159 URL: https://issues.apache.org/jira/browse/HBASE-19159 Project: HBase Issue Type:

[jira] [Created] (HBASE-19158) Ref guide needs upgrade update

Sean Busbey created HBASE-19158: --- Summary: Ref guide needs upgrade update Key: HBASE-19158 URL: https://issues.apache.org/jira/browse/HBASE-19158 Project: HBase Issue Type: Task

Problem with double shading in hbase-thirdparty and hbase-shaded-client?

Mike from another thread asked about shading jackson into hbase-thirdparty. That reminded me of a question I was thinking recently, in conjunction with HBASE-18800 "[Propaganda] Push shaded hbase-client as gateway to an hbase cluster going forward". We have shaded artifacts in hbase-thirdparty

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

Hello, > There is no way to validate correctness of backup in a general case. If there is no way to validate correctness, can we trust them ? > I am waiting for response from feature requester on what they expect from verification. A client using hbase backups should be able to justify its

[jira] [Created] (HBASE-19157) IntegrationTestBackupRestore should warn about missing config

Ted Yu created HBASE-19157: -- Summary: IntegrationTestBackupRestore should warn about missing config Key: HBASE-19157 URL: https://issues.apache.org/jira/browse/HBASE-19157 Project: HBase Issue

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

On doc, We have great doc attached to HBASE-7912 (unfortunately, it is a little bit obsolete now) On Thu, Nov 2, 2017 at 10:31 AM, Vladimir Rodionov wrote: > >>To be clear, I wasn't listing requirements. I was having trouble with > the > >>absolute "There is no way to

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

>>To be clear, I wasn't listing requirements. I was having trouble with the >>absolute "There is no way to validate correctness of backup in a general >>case." I am waiting for response from feature requester on what they expect from verification. Until then, I would rephrase my statement: "I do

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

I backported HBASE-18705. St.Ack On Thu, Nov 2, 2017 at 10:05 AM, Stack wrote: > Thank you Guanghao. Let me see about getting the issue backported. Are you > a +/- 1 sir? Thanks for the digging. > S > > On Thu, Nov 2, 2017 at 1:31 AM, Guanghao Zhang wrote:

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

Thank you Guanghao. Let me see about getting the issue backported. Are you a +/- 1 sir? Thanks for the digging. S On Thu, Nov 2, 2017 at 1:31 AM, Guanghao Zhang wrote: > There is already a issue HBASE-18705 > about this

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

On Thu, Nov 2, 2017 at 5:51 AM, Josh Elser wrote: > On 11/1/17 11:33 PM, Stack wrote: > >> On Wed, Nov 1, 2017 at 5:08 PM, Vladimir Rodionov >> wrote: >> >> There is no way to validate correctness of backup in a general case. >>> >>> You can restore

[jira] [Created] (HBASE-19156) Duplicative regions_per_server options on LoadTestTool

Josh Elser created HBASE-19156: -- Summary: Duplicative regions_per_server options on LoadTestTool Key: HBASE-19156 URL: https://issues.apache.org/jira/browse/HBASE-19156 Project: HBase Issue

[jira] [Created] (HBASE-19155) Store the smallest read point which is used when flush/compaction into the metadata of StoreFile

Duo Zhang created HBASE-19155: - Summary: Store the smallest read point which is used when flush/compaction into the metadata of StoreFile Key: HBASE-19155 URL: https://issues.apache.org/jira/browse/HBASE-19155

[jira] [Resolved] (HBASE-17143) Scan improvement

[ https://issues.apache.org/jira/browse/HBASE-17143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-17143. --- Resolution: Fixed Assignee: Duo Zhang Fix Version/s: (was: 3.0.0)

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

+1 (non-binding), found 1 issue. Checked signatures, sums - OK Built from source tar and git tag (Oracle JDK 1.8.0_151, Maven 3.5.2) - OK Rat check - OK Starting standalone server from bin tar - OK LTT with 1M rows - OK LICENSE, NOTICE - OK Problem: Starting standalone server after building from

[jira] [Created] (HBASE-19154) Scan consistency guarantee

Duo Zhang created HBASE-19154: - Summary: Scan consistency guarantee Key: HBASE-19154 URL: https://issues.apache.org/jira/browse/HBASE-19154 Project: HBase Issue Type: Umbrella

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

On 11/1/17 11:33 PM, Stack wrote: On Wed, Nov 1, 2017 at 5:08 PM, Vladimir Rodionov wrote: There is no way to validate correctness of backup in a general case. You can restore backup into temp table, but then what? Read rows one-by-one from temp table and look them up

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

That's quite a good argument :) -- there's a difference between occasional verification for building confidence and full data verification for every, single, backup (which is how HBASE-19106 read to me). I still think the latter (thus, 19106, verbatim in its ask) would be unwieldy; however,

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

There is already a issue HBASE-18705 about this problem. But it was only pushed to master branch. 2017-11-02 15:21 GMT+08:00 Guanghao Zhang : > Updated f="${HBASE_HOME}/target/cached_classpath.txt" to >

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

Updated f="${HBASE_HOME}/target/cached_classpath.txt" to f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt". Then start hbase success. Anything wrong for my environment? Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T00:41:47+08:00) Maven home:

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

Download src and build pass. But when start-hbase.sh, I found the master can't start in standalone mode. ``` running master, logging to /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out As this is a development environment, we need

Re: [ANNOUNCE] Please welcome new HBase committer Rahul Gidwani (churro)

Congratulations! 2017-11-02 14:04 GMT+08:00 Pankaj kr : > Congratulation Rahul .. :) > > Regards, > Pankaj > > > -Original Message- > From: Andrew Purtell [mailto:apurt...@apache.org] > Sent: Saturday, October 28, 2017 5:45 AM > To: dev@hbase.apache.org > Subject:

RE: [ANNOUNCE] Please welcome new HBase committer Rahul Gidwani (churro)

Congratulation Rahul .. :) Regards, Pankaj -Original Message- From: Andrew Purtell [mailto:apurt...@apache.org] Sent: Saturday, October 28, 2017 5:45 AM To: dev@hbase.apache.org Subject: [ANNOUNCE] Please welcome new HBase committer Rahul Gidwani (churro) On behalf of the Apache

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

On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser wrote: > +1 (binding) > > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource, > TestReplicaWithCluster, TestReplicationAdmin, and TestRegionServerHostname > consistently fail for me locally (commented on HBASE-19147) >