SLO upload doesn't check /info before sending

Bug #1524465 reported by Douglas Soltesz
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
python-swiftclient
In Progress
Undecided
Cheng Li

Bug Description

When uploading a SLO Swiftclient sends the data first to the multipart_segments then creates the SLO manifest.

This fails if:
    the SLO segments exceed the max allowed segments
    the SLO segment size is larger than the size specified by the user
    SLO middleware is not enabled

However, by the time this is detected, my time and bandwidth have been wasted.
If swiftclient was to check /info before sending SLO/DLOs the system can abort before the transfer.

Thanks,

Doug

Revision history for this message
Tim Burke (1-tim-z) wrote :

Also note that in some (all?) of these situations, the orphaned segments are left on the server!

Changed in python-swiftclient:
status: New → Confirmed
Revision history for this message
Cheng Li (shcli) wrote :

What't the second case of these three? Could you please provide an example?

Revision history for this message
Douglas Soltesz (dsoltesz) wrote :

Example for the second case:
the SLO segment size is larger than the size specified by the user

The default minimum segment size for SLO is 1MB, however this can be changed by the Swift Administrator.

A user uploading an SLO with --segment-size set below 1MB or below the minimum allowed would again fail.

The following information is available in the /info for SLO.

  "slo" : {
      "max_manifest_segments" : 1000,
      "max_manifest_size" : 2097152,
      "min_segment_size" : 1048576
   },

Cheng Li (shcli)
Changed in python-swiftclient:
assignee: nobody → Cheng Li (shcli)
Cheng Li (shcli)
Changed in python-swiftclient:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-swiftclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/297958

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.