[
https://issues.apache.org/jira/browse/HBASE-18463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103784#comment-16103784
]
Dave Latham commented on HBASE-18463:
-------------------------------------
Are we warning because these types of operations are harmful or dangerous? It
seems like if they are, maybe we should change replication to avoid them, but
if they are not, then we shouldn't be warning about them.
> 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
(v6.4.14#64029)
