[
https://issues.apache.org/jira/browse/SOLR-10740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022634#comment-16022634
]
John Stratoulis commented on SOLR-10740:
----------------------------------------
Another approach would be to alter the
{code:java}DistributedUpdateProcessor.getCollectionUrls{code} method that
gathers the nodes to be commited
> SolrCloud should allow non distributed core optimize
> ----------------------------------------------------
>
> Key: SOLR-10740
> URL: https://issues.apache.org/jira/browse/SOLR-10740
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 5.5.1, 6.0.1, 6.5.1
> Environment: Platform indepedent
> Reporter: John Stratoulis
>
> Optimize command does not honor distrib=false option. So all collection
> replicas are getting updated. However there are situations that this is not
> possible.
> At first optimization was done serially, maybe this could help for the
> desired behavior? e.g select only the appropriate core in the nodes commit
> iterration?
> (https://issues.apache.org/jira/browse/SOLR-6264)
> Also by looking down the DistributedUpdateProcessor code there is a rather
> undocumented param named commit_end_point (line: 1898) that seems to do a
> local commit, could this be the solution to the problem?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
