[
https://issues.apache.org/jira/browse/SOLR-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126266#comment-18126266
]
ASF subversion and git services commented on SOLR-18502:
--------------------------------------------------------
Commit f3a798e424bb933ba988c8d316d0e8f35c8b6e0f in solr's branch
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=f3a798e424b ]
SOLR-18502: INSTALLSHARD skips write.lock download (#5026)
> INSTALLSHARD (and RESTORE) should skip write.lock when copying index files
> --------------------------------------------------------------------------
>
> Key: SOLR-18502
> URL: https://issues.apache.org/jira/browse/SOLR-18502
> Project: Solr
> Issue Type: Improvement
> Components: Backup/Restore
> Affects Versions: main(11.0), 9.10.1
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The offline indices that INSTALLSHARD copies into the shard leader probably
> shouldn't contain "write.lock" files, but they commonly do. This doesn't
> cause errors per se - INSTALLSHARD handles these files fine. But it can be a
> bit noisy logging wise, as Solr warns on these files as they don't have the
> checksum footer that Solr/Lucene expects of index files.
> It'd be an nice quality of life improvement if INSTALLSHARD was smart enough
> to skip over these files if they exist, rather than cluttering up the logs
> with false-positive "WARN" messages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
