[
https://issues.apache.org/jira/browse/HBASE-20942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595439#comment-16595439
]
Andrew Purtell commented on HBASE-20942:
----------------------------------------
What we can't abide is something committed somewhere with the JIRA still open.
This is incorrect. The change has been committed (at least somewhere). Then the
RM comes along and tries to make a release and JIRA state is wrong.
I'd be happy to revert all commits prior to rolling the RC that correspond to
unresolved JIRAs if you'd prefer.
> Improve RpcServer TRACE logging
> -------------------------------
>
> Key: HBASE-20942
> URL: https://issues.apache.org/jira/browse/HBASE-20942
> Project: HBase
> Issue Type: Task
> Components: Operability
> Affects Versions: 2.1.0, 1.4.6
> Reporter: Esteban Gutierrez
> Assignee: Krish Dey
> Priority: Major
> Fix For: 3.0.0, 1.5.0, 1.3.3, 2.2.0, 2.1.1, 2.0.2, 1.4.7
>
> Attachments: HBASE-20942.002.patch, HBASE-20942.003.patch,
> HBASE-20942.004.patch, HBASE-20942.005.patch
>
>
> 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]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
