[
https://issues.apache.org/jira/browse/TS-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280217#comment-13280217
]
Otto van der Schaaf commented on TS-1250:
-----------------------------------------
@James: taking a long time is fine, crashing is not (and hanging indefinitly
isn't either. i have not experienced that tough). i don't think the user
interface is capable of handling large amounts of documents either.. so maybe
the regex lookup should just be dropped? Or it's results truncated? A timeout
argument to the cache scan might be nice to have too.
I have found purging using regexes usefull, but i stopped using that, as it
caused crashes.
One other thing, unrelated to this issue: when performing a search with
multiple disks, it doesn't seem that trafficserver parallizes the search. I see
massive i/o on one disk for a few seconds, followed by massive i/o on another
disk.
@Leif:
That sounds awefully usefull.
> Cache inspector does not seem to work properly
> ----------------------------------------------
>
> Key: TS-1250
> URL: https://issues.apache.org/jira/browse/TS-1250
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Leif Hedstrom
> Assignee: James Peach
> Priority: Critical
> Fix For: 3.1.4
>
>
> It seems the cache inspector is not functioning properly. Regex lookups
> mostly works, but individual URLs does not. When it displays the error
> results page from a lookup, it also tends to truncate the URL by one
> character.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
