[
https://issues.apache.org/jira/browse/HBASE-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530203#comment-13530203
]
Sergey Shelukhin commented on HBASE-7317:
-----------------------------------------
Hmm, somehow I missed that in the book. That looks very useful :)
I have looked at the source a bit; is there any good way to add debug
information to Span-s, e.g. exceptions/etc.?
As far as I understand it currently would trace operation starts/ends, right?
>From the patch in the JIRA that adds the hooks, it looks like more hooks
>should be added.
Wrt placement, is there a reason to not put it into org.apache.common..., with
only HDFS/HBase/etc. specific receivers living in their corresponding projects?
I can do it when I have bandwidth if there are no legal/procedural objections
or objections from the author.
> server-side request problems are hard to debug
> ----------------------------------------------
>
> Key: HBASE-7317
> URL: https://issues.apache.org/jira/browse/HBASE-7317
> Project: HBase
> Issue Type: Brainstorming
> Components: IPC/RPC, regionserver
> Reporter: Sergey Shelukhin
> Priority: Minor
>
> I've seen cases during integration tests where the write or read request took
> an unexpectedly large amount of time (that, after the client went to the
> region server that is reported alive and well, which I know from temporary
> debug logging :)), and it's impossible to understand what is going on on the
> server side, short of catching the moment with jstack.
> Some solutions (off by default) could be
> - a facility for tests (especially integration tests) that would trace
> Server/Master calls into some log or file (won't help with internals but at
> least one could see what was actually received);
> - logging the progress of requests between components inside master/server
> (e.g. "request id=N received", "request id=N is being processed in MyClass",
> N being drawn on client from local sequence - no guarantees of uniqueness are
> necessary).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
