[
https://issues.apache.org/jira/browse/HBASE-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528467#comment-16528467
]
Sergey Soldatov commented on HBASE-20826:
-----------------------------------------
[[email protected]] Actually my point is that this problem should be handled
on both sides. So I'm happy with the suggested patch as well as I'm going to do
some work on Phoenix side as well. I just want to be sure that I would have a
full log with TRACE level (sometimes we need to find duplicated values in the
filter and it would not be possible without it).
> 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)
