[
https://issues.apache.org/jira/browse/SOLR-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Aiyengar resolved SOLR-6275.
-------------------------------------
Resolution: Fixed
I have removed the full test, mainly because it has grinded through for a while
now, and only MacOSX seems to be failing mostly.
At this point, this seems to be mostly testing (and failing) on OS scheduling
due to the Jenkins machine running at full CPU usage.
FWIW, the slow/non-monotonic nanoTime issue on MacOSX is now resolved..
https://bugs.openjdk.java.net/browse/JDK-8040140, and I have seen these
failures with the fix applied (on Java 8) and without (on Java 7) -- so it
seems mainly due to scheduling.
> Improve accuracy of QTime reporting
> -----------------------------------
>
> Key: SOLR-6275
> URL: https://issues.apache.org/jira/browse/SOLR-6275
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Ramkumar Aiyengar
> Assignee: Ramkumar Aiyengar
> Priority: Minor
> Fix For: 5.1
>
> Attachments: SOLR-6275.patch
>
>
> Currently, {{QTime}} uses {{currentTimeMillis}} instead of {{nano Time}} and
> hence is not suitable for time measurements. Further, it is really started
> after all the dispatch logic in {{SolrDispatchFilter}} (same with the top
> level timing reported by {{debug=timing}}) which may or may not be expensive,
> and hence may not fully represent the time taken by the search. This is to
> remedy both cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
