[
https://issues.apache.org/jira/browse/SOLR-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-18083:
----------------------------------
Labels: pull-request-available (was: )
> Fix behavior of normal operations for readOnly collections
> ----------------------------------------------------------
>
> Key: SOLR-18083
> URL: https://issues.apache.org/jira/browse/SOLR-18083
> Project: Solr
> Issue Type: Bug
> Reporter: Houston Putman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently there are issues when trying to do a number of things when a
> collection is in ReadOnly state, namely because Solr tries to issue a commit
> or refuses to open an indexWriter. These things make recovery or restarting a
> node impossible when a collection is in a readOnly state.
> While a core is reloaded and put into read-only state, a commit is issued. So
> we can probably assume that all read-only collections have cores that are
> already committed. (If this is not a valid assumption, we should fix Solr so
> that it is valid). Thus whenever we try to issue a commit at various points
> (especially during recovery), we should make sure that we are not in
> read-only mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
