[
https://issues.apache.org/jira/browse/HBASE-12937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295417#comment-14295417
]
James Taylor commented on HBASE-12937:
--------------------------------------
My thinking was that HTrace is not going to know when to reset the thread local
state through Tracer.getInstance().continueSpan(null), while a client (HBase in
this case) would. Is that not the case, [~stack]?
> Infinite tracing loop brings down region server
> -----------------------------------------------
>
> Key: HBASE-12937
> URL: https://issues.apache.org/jira/browse/HBASE-12937
> Project: HBase
> Issue Type: Bug
> Reporter: James Taylor
>
> See HTRACE-92 for more detail. I'm hoping that adding calls to
> Tracer.getInstance().continueSpan(null) in the correct place(s) will do the
> trick. This is rendering tracing unusable by Phoenix. Not sure if it impact
> general HTrace use in HBase or not.
> FYI, [~samarthjain], [~jesse_yates].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
