You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Houston Putman (Jira)" <ji...@apache.org> on 2021/10/21 19:49:00 UTC

[jira] [Created] (SOLR-15711) Fix GCSRepository to follow BackupRepository.createDirectory API contract

Houston Putman created SOLR-15711:
-------------------------------------

             Summary: Fix GCSRepository to follow BackupRepository.createDirectory API contract
                 Key: SOLR-15711
                 URL: https://issues.apache.org/jira/browse/SOLR-15711
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
          Components: contrib - GCS Repository
            Reporter: Houston Putman


Noticed when doing work for SOLR-15702.

The Solr backup commands call {{BackupRepository.createDirectory}} at various times, while also checking that the same directory exists (via {{pathExists}}) at different times. The issue here is that during the distributed Backup commands, (sent to different nodes for each shard), one node might be at the part of the backup where it is calling {{createDirectory}} when another node is calling {{pathExists}} for the same directory. 

When following the BackupRepository API Spec correctly, this should not be an issue because {{createDirectory}} should be a no-op when the directory already exists. However {{GCSRepository}} does not make this check before creating the directory. This should be an easy fix.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org