[
https://issues.apache.org/jira/browse/SOLR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120301#comment-13120301
]
Yonik Seeley commented on SOLR-2809:
------------------------------------
bq. I'm not sure we can combine the approaches but maybe...
Yeah, Solr has had it's own searcher management since '04... I'm not sure it's
practical to try and replace it all, esp when it seems so easy to build leases
on top of that and not touch it at all.
One thing that comes to mind that we could share is a general purpose class
LeaseManager<Key,LeasedResource>
that simply has a few methods like
{code}
long reserve(LeasedResource resource, long ms)
LeasedResource lookup(Key key)
void clearAll()
{code}
Instead of LeasedResource, perhaps it could just be LeaseManager<Key,
Closeable>() as I think close() is the only thing that a LeaseManager would
need to call?
> searcher leases
> ---------------
>
> Key: SOLR-2809
> URL: https://issues.apache.org/jira/browse/SOLR-2809
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
>
> Leases/reservations on searcher instances would give us the ability to use
> the same searcher across phases of a distributed search, or for clients to
> send multiple requests and have them hit a consistent/unchanging view of the
> index. The latter requires something extra to ensure that the load balancer
> contacts the same replicas as before.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
