[
https://issues.apache.org/jira/browse/HBASE-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530424#comment-13530424
]
Todd Lipcon commented on HBASE-7317:
------------------------------------
bq. That's disappointing. Then my concern about depending on a project in this
state stands.
What do you mean? If there are bugs in the code, feel free to submit patches,
and I'm happy to integrate them (I have commit access to the repo). If we end
up with several contributors, I don't foresee any issues proposing it for
Apache incubation.
> 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
