[
https://issues.apache.org/jira/browse/HTRACE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe updated HTRACE-328:
----------------------------------------
Description:
htraced continues scanning in some cases even when no more results are possible.
The clearest example of this is doing a point query on a span id. It should be
just seeking to where the span would be (if it existed) and then either reading
it or returning "not found." Instead, it scans the whole leveldb database.
This can be quite slow on larger leveldb instances.
was:
I have a test HTraced instance up. using the gui to search for "span id is"
takes ~2 minutes.
If I use the up/down arrows to expand trace parents/children the return is
nearly instantaneous.
> htraced continues scanning in some cases even when no more results are
> possible
> -------------------------------------------------------------------------------
>
> Key: HTRACE-328
> URL: https://issues.apache.org/jira/browse/HTRACE-328
> Project: HTrace
> Issue Type: Bug
> Components: htraced
> Affects Versions: 4.1
> Reporter: Sean Busbey
> Assignee: Colin Patrick McCabe
> Priority: Critical
>
> htraced continues scanning in some cases even when no more results are
> possible.
> The clearest example of this is doing a point query on a span id. It should
> be just seeking to where the span would be (if it existed) and then either
> reading it or returning "not found." Instead, it scans the whole leveldb
> database. This can be quite slow on larger leveldb instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
