using Solr S3 backup with a Netapp

["Olson, Robert D." <ol...@mcs.anl.gov>]

Hi all – I’m trying to make the Solr S3 backup work using a Netapp appliance that speaks S3.

It feels like the auth stuff is all properly working, but I’m getting 403 errors in the Solr log when I trigger a backup.  My solr.xml looks like this:


  <backup>

    <repository name="s3" class="org.apache.solr.s3.S3BackupRepository" default="false">

          <str name="s3.bucket.name">solr9-backup</str>

          <!-- <str name="s3.region">us-east-2</str> -->

          <str name="s3.endpoint">https://REDACTED:18082</str<https://REDACTED:18082%3c/str>>

    </repository>

  </backup>

The invocation is  a curl to this URL:

https://[REDACTED-SOLR]:15183/solr/admin/collections?action=BACKUP&collection=genome&name=genome&s3.bucket.name=&s3.endpoint=[REDACTED]:18082&location=genome&async=2024-09-09-17-39-08


I figured out how to enable wire protocol debugging, and I’m indeed getting a 404


2024-09-09 22:40:28.657 DEBUG (qtp1257299717-124-bio-gp.cels.anl.gov-4) [c:genome s: r: x: t:bio-gp.cels.anl.gov-4] o.a.h.wire http-outgoing-4 >> "HEAD /solr9-backup/genome/ HTTP/1.1[\r][\n]"


2024-09-09 22:40:28.703 DEBUG (qtp1257299717-124-bio-gp.cels.anl.gov-4) [c:genome s: r: x: t:bio-gp.cels.anl.gov-4] s.a.a.request Received failed response: 404, Request ID: 1725921628649471, Extended Request ID: 12605632

It seems like that object is there:


$ s3cmd info s3://solr9-backup/genome

s3://solr9-backup/genome (object):

   File size: 0

   Last mod:  Fri, 06 Sep 2024 21:02:31 GMT

   MIME type: inode/x-empty

   Storage:   STANDARD

   MD5 sum:   d41d8cd98f00b204e9800998ecf8427e

   SSE:       none

   Policy:    none

   CORS:      none

   ACL:       CELS-PATRIC: FULL_CONTROL

   x-amz-meta-s3cmd-attrs: atime:1725644332/ctime:1725644326/gid:20001/gname:cels/md5:d41d8cd98f00b204e9800998ecf8427e/mode:33188/mtime:1725644326/uid:10078/uname:svcbvbrc

This feels like there’s a difference in semantics between real S3 and the Netapp. Has anyone seen this?

I need to resurrect my personal S3 account to try the same config against real AWS. Tomorrow.

Thanks,
Bob