Is this expected HBase replication behavior or am I doing something wrong?

2017-03-30 Thread James Johansville
Hello, I attempted HBase replication for the first time and am trying to understand how it works. I have three HBase clusters each with their own ZK ensemble, A, B, C. I wanted to have complete acyclical replication between all 3 clusters, so I added B as a peer of A, C as a peer of B, A as a

Re: Re: Poor performance of table Increment

2016-07-09 Thread James Johansville
I had the same issue. I ended up writing a coprocessor that did this under the BatchMutate hood using a special attribute in the Put operation, and that increased performance significantly to be almost equal to the regular batchMutate(Put) version. On Sat, Jul 9, 2016 at 7:59 AM, 陆巍

Question on writing scan coprocessors

2016-04-27 Thread James Johansville
Hello, I'd like to write a similar coprocessor to the example RegionObserverExample at http://www.3pillarglobal.com/insights/hbase-coprocessors : that is, a scan coprocessor which intercepts and selectively filters scan results. My problem is, I need to be able to filter out Results based on a

Re: Inconsistent scan performance

2016-03-25 Thread James Johansville
Z for example. > > > > > >> On Fri, Mar 25, 2016 at 6:51 AM, Anoop John <anoop.hb...@gmail.com> > > wrote: > > >> > > >> I see you set cacheBlocks to be false on the Scan. By any chance on > > >> some other RS(s), the data you are looking for is alre

Re: Inconsistent scan performance

2016-03-24 Thread James Johansville
I assume the partitions' boundaries don't align with region boundaries, > right ? > > Meaning some partitions would cross region boundaries. > > Which hbase release do you use ? > > Thanks > > On Thu, Mar 24, 2016 at 4:45 PM, James Johansville < > james.joh

Inconsistent scan performance

2016-03-24 Thread James Johansville
Hello all, So, I wrote a Java application for HBase that does a partitioned full-table scan according to a set number of partitions. For example, if there are 20 partitions specified, then 20 separate full scans are launched that cover an equal slice of the row identifier range. The rows are