[
https://issues.apache.org/jira/browse/HBASE-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528303#comment-16528303
]
Sergey Soldatov commented on HBASE-20826:
-----------------------------------------
At first place, that should be handled on Filter level as well (so Phoenix
filters should be aware that they are putting in toString, otherwise it would
spend too much time just building 10-20Mb strings as well as it would increase
the memory pressure). And for the TRACE level we shouldn't truncate anything,
otherwise, it may cause problems with identifying the problem root causes.
Just my 2 cents.
> Truncate responseInfo attributes on RpcServer WARN messages
> -----------------------------------------------------------
>
> Key: HBASE-20826
> URL: https://issues.apache.org/jira/browse/HBASE-20826
> Project: HBase
> Issue Type: Improvement
> Components: rpc
> Reporter: Sergey Soldatov
> Assignee: Josh Elser
> Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.2, 2.2.0
>
> Attachments: HBASE-20826.001.branch-2.0.patch,
> HBASE-20826.002.branch-2.0.patch
>
>
> With Phoenix in the picture, dumping the {{Call}} protobuf to the RS log can
> get *really* chatty, real fast. Notably, some serialized filters just spam
> the log with binary garbage.
> Let's add an upper-limit to the length of params we'll put out at WARN, and
> leave the full content for TRACE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
