[HBASE-20942] Improve RpcServer TRACE logging

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0, 1.4.6
• Fix Version/s: 3.0.0-alpha-1, 1.3.3, 2.2.0, 2.0.2, 1.4.7
• Component/s: Operability
• Release Note: Allows configuration of the length of RPC messages printed to the log at TRACE level via "hbase.ipc.trace.param.size" in RpcServer.
• Assignee: Krish Dey
• Reporter: Esteban Gutierrez
• Created: 25/Jul/18 20:28
• Updated: 01/Feb/19 20:32
• Resolved: 28/Aug/18 18:48

Description

Two things:

• We truncate RpcServer output to 1000 characters for trace logging. Would be better if that value was configurable.
• There is the chance for an ArrayIndexOutOfBounds when truncating the TRACE log message.

Esteban mentioned this to me earlier, so I'm crediting him as the reporter.

cc: elserj

Issue Links

• is cloned by: HBASE-21125 Backport 'HBASE-20942 Improve RpcServer TRACE logging' to branch-2.1
• is duplicated by: HBASE-21108 RpcServer when trace enabled might get the following exception. java.lang.StringIndexOutOfBoundsException:
• is related to: HBASE-21108 RpcServer when trace enabled might get the following exception. java.lang.StringIndexOutOfBoundsException:
• is related to: HBASE-20826 Truncate responseInfo attributes on RpcServer WARN messages