Re: [jira] [Resolved] (HBASE-14036) HBase Backup/Restore Phase 1: Custom WAL archive cleaner

Do you think its time to stop sending files one by one to the cleaners and have all the cleaners take batches of files (like replication and snapshot cleaners)? As we add more cleaners for large clusters and certain scenarios the cleaner chain comes to a crawl? On Fri, Jul 17, 2015 at 3:28 PM, Vl

[jira] [Created] (HBASE-14119) Show error message instead of stack traces in hbase shell commands

Apekshit Sharma created HBASE-14119: --- Summary: Show error message instead of stack traces in hbase shell commands Key: HBASE-14119 URL: https://issues.apache.org/jira/browse/HBASE-14119 Project: HBa

Re: Why TableNamespaceManager#upsert abort master if failing to update zookeeper

I think the master is aborting because the listeners on that zknode will have the wrong information. so aborting was probably a shortcut to say, something went wrong we don't know what to do. hope that on restart and maybe via hbck the state will be fixed. with proc-v2 you don't need to abort, but

Why TableNamespaceManager#upsert abort master if failing to update zookeeper

I am working on moving namespace DDL to Proc-V2 and come to see this code. Looks like the logic exists since St.Ack implemented namespace in HBASE-8408. I just wonder whether the failure of zookeeper update is serve enough to shut down master (in my new code, I don't abort - I want to make sure th

[jira] [Resolved] (HBASE-14037) Deletion of a table from backup set results int RTE during next backup

[ https://issues.apache.org/jira/browse/HBASE-14037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-14037. --- Resolution: Fixed The fix is part of patch v4. See parent JIRA. > Deletion of a tabl

[jira] [Resolved] (HBASE-14036) HBase Backup/Restore Phase 1: Custom WAL archive cleaner

[ https://issues.apache.org/jira/browse/HBASE-14036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-14036. --- Resolution: Implemented This feature is part of patch v4. See parent JIRA. > HBase B

[jira] [Resolved] (HBASE-14040) Small refactoring in BackupHandler

[ https://issues.apache.org/jira/browse/HBASE-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-14040. --- Resolution: Won't Fix Not sure if it is worth doing. Too much code change for the sak

[jira] [Resolved] (HBASE-14038) Incremental backup list set is ignored during backup

[ https://issues.apache.org/jira/browse/HBASE-14038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-14038. --- Resolution: Later Will work on this later in Phase 2. > Incremental backup list set

Re: [VOTE] Merge branch hbase-11339 HBase MOB to trunk

+1 On Fri, Jul 17, 2015 at 2:01 AM, Jingcheng Du wrote: > Hi all, > > The Moderate Object Storage (MOB) feature (HBASE-11339[1]) is modified I/O > and compaction path that allows individual moderately sized values > (100KB-10MB) to be stored so that write amplification is reduced when > compared

Fwd: Hbase Fully distribution mode - Cannot resolve regionserver hostname

+user@, dev@ to bcc Pubudu, I think you'll get more help on an issue like this on the users list. -Dima -- Forwarded message -- From: Ted Yu Date: Fri, Jul 17, 2015 at 5:40 AM Subject: Re: Hbase Fully distribution mode - Cannot resolve regionserver hostname To: "dev@hbase.apach

[jira] [Resolved] (HBASE-14039) BackupHandler.deleteSnapshot MUST use HBase Snapshot API

[ https://issues.apache.org/jira/browse/HBASE-14039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-14039. --- Resolution: Invalid Closing as invalid, will reopen later once we find any issues wit

[jira] [Created] (HBASE-14118) minicluster maven plugin

Jesse Yates created HBASE-14118: --- Summary: minicluster maven plugin Key: HBASE-14118 URL: https://issues.apache.org/jira/browse/HBASE-14118 Project: HBase Issue Type: New Feature Comp

Re: DISCUSSION: lets do a developer workshop on near-term work

> I can represent your side Ram (and Anoop). I've been known always argue both > side of a discussion and to never take sides easily (drives some folks crazy). I can vouch for this (smile) I also can offer support for off heaping there. At the same time we do have a gap where we can't point to

Re: 0.98 patch acceptance criteria discussion

> So "newer" has some extra meaning. In practice it seems to mean the a > release is "newer" if it's from a minor branch that was branched at a > later date. That's a hard thing for a user to know. How do we meet > the user's expectation with that definition? We need to make it > visible. Give

Re: 0.98 patch acceptance criteria discussion

My thoughts on the patches and versions issue. Apologies as this overlaps some of what others said, since I got the notes in order. All of this stems from trying to make life easier for our users and meet their expectations. Here's what I think are the relevant user expectations: - Upgrading to

Re: 0.98 patch acceptance criteria discussion

> I think the extra statement we have to make is that only the latest minor version of the next major branch > is guaranteed have all the improvements of the previous major branch.Or phrased in other words: > Improvements that are not bug fixes will only go into the x.y.0 minor version, but not (by

Re: DISCUSSION: lets do a developer workshop on near-term work

I'm in favor of anything that improves performance (and preferably doesn't set us back into a world that's worse than C due to the lack of pointers in Java).Never said "I don't like it", it's just that I'm perhaps asking for more numbers and justification in weighing the pros and cons. I can rep

Re: How to generate thrift classes ?

Thanks Ram. I will try this. Regards, Ashish On Fri, Jul 17, 2015 at 6:42 PM, ramkrishna vasudevan < ramkrishna.s.vasude...@gmail.com> wrote: > Sorry forgot to attach the link > > http://wiki.apache.org/hadoop/Hbase/ThriftApi > > Regards > Ram > > On Fri, Jul 17, 2015 at 6:04 PM, ramkrishna vas

Re: 0.98 patch acceptance criteria discussion

Thanks Andy. I think the gist of the discussion boils down to this:We generally have two goals: (1) follow semver from 1.0.0 onward and (2) avoid losing features/improvements when upgrading from an older version to a newer one. Turns out these two are conflicting unless we follow certain addition

Re: How to generate thrift classes ?

Sorry forgot to attach the link http://wiki.apache.org/hadoop/Hbase/ThriftApi Regards Ram On Fri, Jul 17, 2015 at 6:04 PM, ramkrishna vasudevan < ramkrishna.s.vasude...@gmail.com> wrote: > Hi Ashish > > I have tried adding thrift files for some cases while doing Tags and > visibility labels. >

[jira] [Created] (HBASE-14117) Check DBEs where fields are being read from Bytebuffers but unused.

ramkrishna.s.vasudevan created HBASE-14117: -- Summary: Check DBEs where fields are being read from Bytebuffers but unused. Key: HBASE-14117 URL: https://issues.apache.org/jira/browse/HBASE-14117

[jira] [Created] (HBASE-14116) Change ByteBuff.getXXXStrictlyForward to relative position based reads

ramkrishna.s.vasudevan created HBASE-14116: -- Summary: Change ByteBuff.getXXXStrictlyForward to relative position based reads Key: HBASE-14116 URL: https://issues.apache.org/jira/browse/HBASE-14116

Re: How to generate thrift classes ?

Hi Ashish I have tried adding thrift files for some cases while doing Tags and visibility labels. Pls take a look at this link for reference - may be it is obselete but could be helpful. Take a look at HBASE-9884 for the sample case. It is like the protobuf changes that we do. We will have the

How to generate thrift classes ?

Hi devs. I want to remove Iface#getRowOrBefore api as part of HBASE-13954. The doc on top of the class says "Autogenerated by Thrift Compiler (0.9.0)". So I think, I should not remove it manually there should be some way to generate this class. Can any one please explain me how to generate thrift

Re: Hbase Fully distribution mode - Cannot resolve regionserver hostname

Have you looked at HBASE-12954 Ability impaired using HBase on multihomed hosts Cheers On Fri, Jul 17, 2015 at 3:32 AM, Pubudu Gunatilaka wrote: > Hi Devs, > > I am trying to run Hbase in fully distributed mode. So first I started > master node. Then I started regionserver. But I am getting fol

Re: [VOTE] Merge branch hbase-11339 HBase MOB to trunk

QA run for HBASE-11339 is green. IntegrationTestIngestWithMOB has been run which passes. +1 on merging to master branch. On Fri, Jul 17, 2015 at 2:01 AM, Jingcheng Du wrote: > Hi all, > > The Moderate Object Storage (MOB) feature (HBASE-11339

Hbase Fully distribution mode - Cannot resolve regionserver hostname

Hi Devs, I am trying to run Hbase in fully distributed mode. So first I started master node. Then I started regionserver. But I am getting following error. 2015-07-17 05:12:02,260 WARN [pod-35:16020.activeMasterManager] master.AssignmentManager: Failed assignment of hbase:meta,,1.1588230740 to p

Re: [DISCUSSION] Merge of the hbase-11339 mob branch into master.

Thanks Ted. The VOTE mail was posted a while ago. Regards Jingcheng -- View this message in context: http://apache-hbase.679495.n3.nabble.com/DISCUSSION-Merge-of-the-hbase-11339-mob-branch-into-master-tp4071644p4073309.html Sent from the HBase Developer mailing list archive at Nabble.com.

[VOTE] Merge branch hbase-11339 HBase MOB to trunk

Hi all, The Moderate Object Storage (MOB) feature (HBASE-11339[1]) is modified I/O and compaction path that allows individual moderately sized values (100KB-10MB) to be stored so that write amplification is reduced when compared to the normal I/O path. MOB is defined in the column family and it

[jira] [Created] (HBASE-14115) Fix resource leak in HMasterCommandLine

Yuhao Bi created HBASE-14115: Summary: Fix resource leak in HMasterCommandLine Key: HBASE-14115 URL: https://issues.apache.org/jira/browse/HBASE-14115 Project: HBase Issue Type: Bug R