[jira] [Resolved] (HBASE-7317) consider "full-featured" support for HTrace for HBase debugging

["Andrew Kyle Purtell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-7317.
----------------------------------------
    Resolution: Duplicate

[~ndimiduk] et al work with OpenTracing in 2.5 and up supersedes this issue.

> consider "full-featured" support for HTrace for HBase debugging
> ---------------------------------------------------------------
>
>                 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 was sent by Atlassian Jira
(v8.20.7#820007)