[jira] [Created] (HBASE-15393) Enable table replication command will fail when parent znode is not /hbase(default) in peer cluster

Ashish Singhi created HBASE-15393: - Summary: Enable table replication command will fail when parent znode is not /hbase(default) in peer cluster Key: HBASE-15393 URL:

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

Thanks for chiming in Jincheng. Really appreciated. But from this thread, it's apparent that people don't have enough enthusiasm to see this backported in branch-1. So, maybe what would be really nice to instead do is to make sure that MOB is performant / reliable / releasable in the HBASE-2.0

[jira] [Created] (HBASE-15392) Single Cell Get reads two HFileBlocks

stack created HBASE-15392: - Summary: Single Cell Get reads two HFileBlocks Key: HBASE-15392 URL: https://issues.apache.org/jira/browse/HBASE-15392 Project: HBase Issue Type: Sub-task

RE: [DISCUSS] Criteria for including MOB feature backport in branch-1

Sorry for the late chime in and thank you all for the discussion. I agree with Jon's suggestion, to make a new branch for MOB in branch-1.x, and backport it when it is definitely ready. I can start to work on that branch after the distributed mob compaction is finished. I think the distributed

[jira] [Created] (HBASE-15391) Avoid too large "deleted from META" info log

Liu Shaohui created HBASE-15391: --- Summary: Avoid too large "deleted from META" info log Key: HBASE-15391 URL: https://issues.apache.org/jira/browse/HBASE-15391 Project: HBase Issue Type:

[jira] [Created] (HBASE-15390) ClientExceptionUtils doesn't handle CallQueueTooBigException properly

Mikhail Antonov created HBASE-15390: --- Summary: ClientExceptionUtils doesn't handle CallQueueTooBigException properly Key: HBASE-15390 URL: https://issues.apache.org/jira/browse/HBASE-15390 Project:

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

Good questions, Enis. If my bandwidth permits, I am planning to collect performance statistics using ycsb against cluster with and without MOB feature enabled. Cheers On Thu, Mar 3, 2016 at 3:49 PM, Enis Söztutar wrote: > Regardless of the backport, did we do the same

[jira] [Created] (HBASE-15389) Write out multiple files when compaction

Duo Zhang created HBASE-15389: - Summary: Write out multiple files when compaction Key: HBASE-15389 URL: https://issues.apache.org/jira/browse/HBASE-15389 Project: HBase Issue Type: Sub-task

[jira] [Created] (HBASE-15388) Add ACL for some master methods

Enis Soztutar created HBASE-15388: - Summary: Add ACL for some master methods Key: HBASE-15388 URL: https://issues.apache.org/jira/browse/HBASE-15388 Project: HBase Issue Type: Bug

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

Regardless of the backport, did we do the same regression analysis for the master branch merge at the time of the merge? Like make sure that the latencies and stability of non-mob is affected or not. Sorry, I was not following the merge vote closely. The reason I am asking is that although we can

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

Just to be clear, I did not actually oppose a backport of MOB. Although - I have to say am sympathetic to Elliott's position that there's a project management reason not to. My insistence here is "merely" for this change in particular a backport to the branch we are making production releases from

[jira] [Resolved] (HBASE-15370) Backport Moderate Object Storage (MOB) to branch-1

[ https://issues.apache.org/jira/browse/HBASE-15370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved HBASE-15370. Resolution: Won't Fix Assignee: (was: Ted Yu) Judging from response from the community, the

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

In the middle of writing response to this thread, I saw subsequent comments from Andrew, Jon and Elliott. In light of opposition from the community w.r.t. backporting MOB feature, I think it suffices to say that this wouldn't be done now. Thanks everyone for chiming in. On Thu, Mar 3, 2016 at

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

I just don't see a why we would back port. We're going to release a 2.0 when things are ready. It will be a major feature release. MOB is a major feature. Without compelling reason backporting to branch-1 seems like an end run around what sem ver is supposed to mean (not the api guarantees, the

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

On Thu, Mar 3, 2016 at 1:01 PM, Stack wrote: > On Thu, Mar 3, 2016 at 9:02 AM, Ted Yu wrote: > > > Hi, > > As requested by Sean Busbey, I am starting a new thread w.r.t. > backporting > > MOB feature to branch-1. > > > This is to solicit discussion on the

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

In addition to Stack's points those of us running HBase in production will need assurance in the form of data collected from a plausible test environment that the MOB backport does not affect function, stability, or performance for anyone who doesn't want it. Furthermore some affirmative

Re: [DISCUSS] Criteria for including MOB feature backport in branch-1

On Thu, Mar 3, 2016 at 9:02 AM, Ted Yu wrote: > Hi, > As requested by Sean Busbey, I am starting a new thread w.r.t. backporting > MOB feature to branch-1. > This is to solicit discussion on the criteria for including MOB feature > backport in branch-1. > > I can think of

Re: Parallel scanning of snapshots using hbase client api

We upgraded the lib version to 5.4.8 and though the parallel scanning exception issue is fixed we see a bigger problem with running multiple scanners. Our intended use for a single scanner was to let the snapshot scanner scan a given range of keys along with the region info they are located on

[jira] [Resolved] (HBASE-15136) Explore different queuing behaviors while busy

[ https://issues.apache.org/jira/browse/HBASE-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-15136. --- Resolution: Fixed Resolving again. Issues have been opened to deal w/ the flakies. Thanks [~mantonov] and

[jira] [Reopened] (HBASE-15136) Explore different queuing behaviors while busy

[ https://issues.apache.org/jira/browse/HBASE-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reopened HBASE-15136: --- Reopening: See how trunk build is failing these new tests mighty [~mantonov]

[DISCUSS] Criteria for including MOB feature backport in branch-1

Hi, As requested by Sean Busbey, I am starting a new thread w.r.t. backporting MOB feature to branch-1. This is to solicit discussion on the criteria for including MOB feature backport in branch-1. I can think of the following: 1. whether there is customer interest There is. See Jonathan's

[jira] [Created] (HBASE-15387) Make HalfStoreFileReader configurable in LoadIncrementalHFiles

Rajeshbabu Chintaguntla created HBASE-15387: --- Summary: Make HalfStoreFileReader configurable in LoadIncrementalHFiles Key: HBASE-15387 URL: https://issues.apache.org/jira/browse/HBASE-15387

Successful: HBase Generate Website

Build status: Successful If successful, the website and docs have been generated. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around

[jira] [Resolved] (HBASE-15385) A failed atomic folder rename operation can never recovery for the destination file is deleted in Wasb filesystem

[ https://issues.apache.org/jira/browse/HBASE-15385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Shaohui resolved HBASE-15385. - Resolution: Invalid Fix Version/s: (was: 3.0.0) > A failed atomic folder rename

[jira] [Created] (HBASE-15386) PREFETCH_BLOCKS_ON_OPEN in HColumnDescriptor is ignored

stack created HBASE-15386: - Summary: PREFETCH_BLOCKS_ON_OPEN in HColumnDescriptor is ignored Key: HBASE-15386 URL: https://issues.apache.org/jira/browse/HBASE-15386 Project: HBase Issue Type:

[jira] [Created] (HBASE-15385) A failed atomic folder rename operation can never recovery for the destination file deleted in Wasb filesystem

Liu Shaohui created HBASE-15385: --- Summary: A failed atomic folder rename operation can never recovery for the destination file deleted in Wasb filesystem Key: HBASE-15385 URL:

[jira] [Resolved] (HBASE-15309) GZIP HFile Compression & Decompression Memory Leak, Similar Issue HBASE-5516

[ https://issues.apache.org/jira/browse/HBASE-15309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] karthik resolved HBASE-15309. - Resolution: Not A Bug Hadoop Flags: Reviewed Fix Version/s: 0.94.28 Fix : Hbase