[
https://issues.apache.org/jira/browse/SOLR-17058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820509#comment-17820509
]
Mikhail Khludnev commented on SOLR-17058:
-----------------------------------------
bq. LRUStatsCache case is not triggered
It's picked randomly see org.apache.solr.search.stats.TestDistribIDF#setUp.
It's reproduced to me with
{{Reproduce with: gradlew :solr:core:test --tests
"org.apache.solr.search.stats.TestDistribIDF.testDisableDistribStats"
-Ptests.jvms=6 -Ptests.haltonfailure=false
"-Ptests.jvmargs=-XX:+UseCompressedOops -XX:+UseSerialGC"
-Ptests.seed=49199A151AFC9EA9}}
bq. restricted to local subordinate
Right.
bq. data change on the subordinate nodes would invalidate the results?
AFAIK, ExactStatsCache requests stats every time (and we can extract into
dedicated testcase with ExactStatsCache), and LRUStatsCache minds timeout.
There's nothing like change tracking/commit visibility.
bq. what other effects shall I test for the QueryResultKey
I'm out off ideas so far.
> Request param to disable distributed stats request at query time
> ----------------------------------------------------------------
>
> Key: SOLR-17058
> URL: https://issues.apache.org/jira/browse/SOLR-17058
> Project: Solr
> Issue Type: New Feature
> Components: query
> Reporter: wei wang
> Assignee: Mikhail Khludnev
> Priority: Minor
> Fix For: 9.6.0
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> When distributed IDF is enabled in solr cloud by adding one of the cache
> implementations in solrconfig.xml
> [https://solr.apache.org/guide/solr/latest/deployment-guide/solrcloud-distributed-requests.html#distributedidf],
> each solr query will incur a distributed shard request to get term
> statistics
> "debug": {
> "track": {
> "rid": "-54",
> "PARSE_QUERY": {
> "http://192.168.0.34:8987/solr/shard2_replica_n1/":
> { "QTime": “2”,
>
> "ElapsedTime": "13",
>
> "RequestPurpose": "GET_TERM_STATS",
> …
>
> For queries that does not use distributed IDF information for scoring
> such as terms filter by id, the stats request is not necessary. Hence I
> propose to add a {{distrib.statsCache}} request param so that the distributed
> stats request can be disabled at query time.
> # {{distrib.statsCache}} defaults to {{{}true{}}}. When the param is not
> present, there is no change to current distributed IDF behavior.
> # When explicitly set {{{}distrib.statsCache{}}}{{{}=false{}}}, distributed
> stats call is disabled for the current query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
