[
https://issues.apache.org/jira/browse/HTRACE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe updated HTRACE-113:
----------------------------------------
Attachment: HTRACE-113.002.patch
here's a version that avoids the exception. I don't think we need a stack
trace for SpanReceiverBuilder since that doesn't happen in more than one place
in either Hadoop or HBase (or really any other htrace client I'm aware of).
> Add more log4j messages to htrace SamplerBuilder, SpanReceiverBuilder, etc.
> ---------------------------------------------------------------------------
>
> Key: HTRACE-113
> URL: https://issues.apache.org/jira/browse/HTRACE-113
> Project: HTrace
> Issue Type: Improvement
> Affects Versions: 3.2.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-113.001.patch, HTRACE-113.002.patch
>
>
> We should add more log4j messages at DEBUG or TRACE level to htrace
> SamplerBuilder, SpanReceiverBuilder, etc. This will make it easier to
> determine which samplers and span receivers are being used by the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
