[
https://issues.apache.org/jira/browse/SOLR-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055237#comment-18055237
]
ASF subversion and git services commented on SOLR-18083:
--------------------------------------------------------
Commit b34a1cb6413bb652c588fb4c403eb77c475dbac9 in solr's branch
refs/heads/branch_10x from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b34a1cb6413 ]
SOLR-18083: Fix replication and other general operations in readOnly mode
(#4088)
(cherry picked from commit 640428af236008d1d3050278c4fbb6ff15d53ad6)
> 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: 2h
> 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]
