[
https://issues.apache.org/jira/browse/LUCENE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-7237:
-----------------------------
Fix Version/s: (was: 6.0)
master (7.0)
Manually correcting fixVersion per Step #S5 of LUCENE-7271
> LRUQueryCache should rather not cache than wait on a lock
> ---------------------------------------------------------
>
> Key: LUCENE-7237
> URL: https://issues.apache.org/jira/browse/LUCENE-7237
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Fix For: 6.1, master (7.0)
>
> Attachments: LUCENE-7237.patch
>
>
> This is an idea Robert just mentioned to me: currently the cache is using a
> lock to keep various data-structures in sync. It is a pity that you might
> have contention because of caching. So something we could do would be to not
> cache when the lock is already taken.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
