hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7317) server-side request problems are hard to debug
Date Wed, 12 Dec 2012 17:54:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530145#comment-13530145

stack commented on HBASE-7317:

bq. Should we be depending on something that only has a single contributor and hasn't seen
a commit in over three months?

Fair point.

Hope was that we'd add tracing to hbase w/ this as a start (and that hadoop itself would be
adding trace I suppose so we could go down into datanodes).  If no progress on tracing before,
say 0.96, yeah, lets remove it.  But maybe there will be progress made in this issue.

Regards a central collector for traces, could try writing an hbase table.
> 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

View raw message