lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-1028) Automatic core loading unloading for multicore
Date Sun, 28 Oct 2012 18:11:12 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485683#comment-13485683
] 

Mark Miller commented on SOLR-1028:
-----------------------------------

Kind of an aside to this specific issue, but in relation to all of these massive number of
SolrCore issues: I'm not sure what I think about all this multi-core work if it's not going
to jive with SolrCloud. Trying to develop Solr as two different systems is too costly in the
long term IMO. My feeling has been that we would push away from the std mode and always run
in SolrCloud mode eventually - it's just a matter of waiting until it's ready. And so introducing
a lot of new work and code that is not compatible with SolrCloud makes me think.

A lot of the ugly warts that are left now are around because we are straddling two different
ways of doing things. The path that makes it all much nicer involves narrowing down to one
way of doing things I think. 

Not quite the right place for the discussion here, but probably one that we should have.
                
> Automatic core loading unloading for multicore
> ----------------------------------------------
>
>                 Key: SOLR-1028
>                 URL: https://issues.apache.org/jira/browse/SOLR-1028
>             Project: Solr
>          Issue Type: New Feature
>          Components: multicore
>            Reporter: Noble Paul
>            Assignee: Erick Erickson
>             Fix For: 4.1
>
>         Attachments: SOLR-1028.patch
>
>
> usecase: I have many small cores (say one per user) on a single Solr box . All the cores
are not be always needed . But when I need it I should be able to directly issue a search
request and the core must be STARTED automatically and the request must be served.
> This also requires that I must have an upper limit on the no:of cores that should be
loaded at any given point in time. If the limit is crossed the CoreContainer must unload a
core (preferably the least recently used core)  
> There must be a choice of specifying some cores as fixed. These cores must never be unloaded


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message