[
https://issues.apache.org/jira/browse/SOLR-17733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-17733:
----------------------------------
Labels: pull-request-available (was: )
> Cluster filestore v2 API fails in cloud mode
> --------------------------------------------
>
> Key: SOLR-17733
> URL: https://issues.apache.org/jira/browse/SOLR-17733
> Project: Solr
> Issue Type: Bug
> Reporter: Colvin Cowie
> Assignee: Eric Pugh
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Calling DELETE /cluster/filestore/files/\{file} results in a 500. The
> implementation of delete cluster file first calls delete local file, but that
> first checks to see if the file exists in the cluster and fails if it does so.
>
> {{10454 ERROR (qtp1073592819-60-null-5) [n:127.0.0.1:56447_solr c: s: r: x:
> t:null-5] o.a.s.j.CatchAllExceptionMapper 500 Exception}}
> {{ => org.apache.solr.common.SolrException:
> org.apache.solr.common.SolrException: The path exists in ZK, delete and
> retry}}
> {{ at
> org.apache.solr.filestore.ClusterFileStore.doClusterDelete(ClusterFileStore.java:282)}}
> {{org.apache.solr.common.SolrException: org.apache.solr.common.SolrException:
> The path exists in ZK, delete and retry}}
> {{ at
> org.apache.solr.filestore.ClusterFileStore.doClusterDelete(ClusterFileStore.java:282)
> ~[main/:?]}}
> {{ at
> org.apache.solr.filestore.ClusterFileStore.doDelete(ClusterFileStore.java:296)
> ~[main/:?]}}
> {{ at
> org.apache.solr.filestore.ClusterFileStore.deleteFile(ClusterFileStore.java:312)
> ~[main/:?]}}
> {{ ...}}
>
> Also when calling POST /cluster/filestore/commands/sync/\{file} it always
> fails with a 500 because the node already exists in ZooKeeper. How can this
> API be used? If it isn't supported in cloud mode then it should return a 501
> (not implemented) or similar, but maybe I'm misunderstanding the intent of
> this API.
>
> See V2APISmokeTest in SOLR-17728
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]