Atleast in trunk it uses SimpleRPCScheduler and internally it tries to use
the Priority based queue so that based on the deadline set for every
request it can schedule the highest priority RPC calls.
I would think that your current requirement may fit with the existing one?
Except that those calls
Scanner prioritization is not sufficient, there are a lot of other IO
activity (compaction, flushing, logging), which can severely affect
high priority scanners.
HBase IO scheduler anyone?
On Wed, May 27, 2015 at 11:26 PM, ashish singhi
wrote:
> Hello folks.
>
> We had a customer scenario to su
We have pluggable RPC scheduler now. See config
'hbase.region.server.rpc.scheduler.factory.class'
By default a SimpleRpcScheduler is in use and there as you said, there are
prioritization for super user. Other prioritization is based on the RS
side method prioritization based on annotation.
You
Hello folks.
We had a customer scenario to support scan priority based on type of request
origin. Consider the scenario , where in n number of scan requests are
generated from different clients. Some of these requests are high priority as
they are originated from high privileged users OR from d
Andrew Purtell wrote
> What coverage do we have for verifying the integrity of MOB references?
> Will the sweep tool detect, alert on, and optionally repair dangling
> references? (I could answer this for myself by looking at MOB branch, but
> hopefully someone here has an answer at the ready.)
Andrew Purtell wrote
> HBCK can check and sideline dangling reference files. I think of MOB files
> as "core enough" auxiliary files that need some support. I suppose unlike
> reference files their presence or absence won't produce a region open
> failure, we would see dangling pointers later wh
bq.So is a MR runtime required for MOB or not? I read maybe, then no, then
here maybe again. What happens if one does not have a MR runtime and
therefore can never run the sweeper tool?
Just to make it clear, now MOB does not have MR dependency. The V1 version
had a sweeper tool that was dependent
I have no concerns about MOB in trunk. Go for it.
I do have concerns about a subsequent proposal to put it in 1.2. Those concerns
center around stability and performance impacts, and a possible dependency on a
MR runtime for what I would consider core function.
> Regarding the tools and integr
Chiming late here,
As Matt suggested earlier, utmost care had been taken to ensure that the
MOB code does not interfere with the normal flow and ensured that things
work normally when MOB is not enabled on a family.
So the entire flow for MOB can be treated as an experimental feature, if
need be.
Inline
On Wednesday, May 27, 2015, Jonathan Hsieh wrote:
> On Sat, May 23, 2015 at 9:40 AM, Andrew Purtell > wrote:
>
> > Regarding performance testing: Whatever has been done on the MOB branch
> > will be interesting data points, and, potentially encouraging, but
> porting
> > to branch-1 will
Inline
On Wednesday, May 27, 2015, Jonathan Hsieh > wrote:
> On Sat, May 23, 2015 at 2:51 PM, Andrew Purtell
> wrote:
>
> > I was responding to this comment from Jon's email:
> >
> > > Another suggestion was a tool to check that mob references had
> > > corresponding mob data. We currently incl
On Sat, May 23, 2015 at 9:40 AM, Andrew Purtell wrote:
> Regarding performance testing: Whatever has been done on the MOB branch
> will be interesting data points, and, potentially encouraging, but porting
> to branch-1 will produce a new code base. Earlier results on other code
> will not be app
On Sat, May 23, 2015 at 2:51 PM, Andrew Purtell wrote:
> I was responding to this comment from Jon's email:
>
> > Another suggestion was a tool to check that mob references had
> > corresponding mob data. We currently include a mr-based sweeper job
> > that could be used to perform this verifica
Matteo Bertozzi created HBASE-13789:
---
Summary: ForeignException should not be sent to the client
Key: HBASE-13789
URL: https://issues.apache.org/jira/browse/HBASE-13789
Project: HBase
Issue
The 1st HBase 0.98.13 release candidate (RC0) is available for
download at http://people.apache.org/~apurtell/0.98.13RC0/ and Maven
artifacts are also available in the temporary repository
https://repository.apache.org/content/repositories/orgapachehbase-1082/
The API compatibility report wit
[
https://issues.apache.org/jira/browse/HBASE-13785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Marc Spaggiari resolved HBASE-13785.
-
Resolution: Invalid
> Provide metrics for average respons size
>
Thanks, makes a lot of sense. I've deleted branch-1.1.0 from the
repository, hopefully this will reduce confusion. The tags remain.
-n
On Fri, May 22, 2015 at 9:34 PM, lars hofhansl wrote:
> Same here.
> Actually for 0.94, I simply spun RCs as tags off the 0.94 branch - hence
> each RC had what
I'll be committing the blocker HBASE-13768 shortly and directly afterward
will make the 0.98.13 RC0 and post it for review. Please let me know if you
have any concerns.
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Dave Latham created HBASE-13788:
---
Summary: Shell does not support column qualifiers containing colon
(:)
Key: HBASE-13788
URL: https://issues.apache.org/jira/browse/HBASE-13788
Project: HBase
Sean Busbey created HBASE-13787:
---
Summary: use a cli argument parsing library instead of ad-hoc
string handling
Key: HBASE-13787
URL: https://issues.apache.org/jira/browse/HBASE-13787
Project: HBase
Sean Busbey created HBASE-13786:
---
Summary: Clean up supplemental ops tools and examples
Key: HBASE-13786
URL: https://issues.apache.org/jira/browse/HBASE-13786
Project: HBase
Issue Type: Umbrel
Jean-Marc Spaggiari created HBASE-13785:
---
Summary: Provide metrics for average respons size
Key: HBASE-13785
URL: https://issues.apache.org/jira/browse/HBASE-13785
Project: HBase
Issue
Jurriaan Mous created HBASE-13784:
-
Summary: Add Async Client Table API
Key: HBASE-13784
URL: https://issues.apache.org/jira/browse/HBASE-13784
Project: HBase
Issue Type: New Feature
23 matches
Mail list logo