hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18463) Replication sink frequently triggers HBASE-18023 warnings
Date Thu, 27 Jul 2017 22:29:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104025#comment-16104025

Andrew Purtell commented on HBASE-18463:

Copied [~elserj] comment from parent:
I could see this go either way:

On one side, replication has its own knobs that control how much data is sent in a single
RPC. This (hopefully) implies that the administrator configured replication to use a certain
batch size and knows that they did this.
On the other side, I would not be surprised at admins who don't set this value and run into
memory/GC issues with RegionServers. I could see this message proactively warning them "hey,
you got some big RPCs coming in" which would hopefully steer them in the right direction.

I would say that if the default configuration values lead us to spamming WARN messages, that
is something we should address in some form.

> Replication sink frequently triggers HBASE-18023 warnings
> ---------------------------------------------------------
>                 Key: HBASE-18463
>                 URL: https://issues.apache.org/jira/browse/HBASE-18463
>             Project: HBase
>          Issue Type: Sub-task
>          Components: regionserver
>            Reporter: Andrew Purtell
>            Priority: Minor
>             Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2
> After HBASE-18023 we warn if the number of operations in a multi operation exceeds a
threshold. This is meant to catch potential performance problems or abusive clients. However
while testing simple replication scenarios we have observed frequent warnings issued as the
sink applies received edit batches. 
> I think we want to either introduce a separate threshold for warning about RPC submitted
by the replication client or exclude ops submitted by the sinks entirely. Not sure distinguishing
the replication client from normal clients is possible yet. 

This message was sent by Atlassian JIRA

View raw message