Object Storage Service:What do I do if the sizes of objects in the source and destination buckets are inconsistent after I configure mirroring-based back-to-origin?

Problem description

After mirroring-based back-to-origin is configured, the sizes of objects in the source and destination buckets are inconsistent.

Solutions

Perform the following steps to troubleshoot the issue:

1. Access the objects stored in the source and destination buckets and compare the results. The following figure provides an example of the result. In the examples, the MD5 hash values of the objects are different.

   Note

   The following URLs are used in the examples:

   • Source: http://kowa-nXXXXXX1.oss-cn-xxxxxxx.aliyuncs.com/uploads/news/2018-03-06/AfmJWdArrx.jpg?x-oss-process=image/resize,m_fill,h_250,w_400

   • Destination: http://kowa-nXXXXXX2.oss-cn-xxxxxxx.aliyuncs.com/uploads/news/2018-03-06/AfmJWdArrx.jpg?x-oss-process=image/resize,m_fill,h_250,w_400

   

2. Confirm that Transfer queryString is selected when you configure mirroring-based back-to-origin.

3. Check whether the sizes of objects in the source and destination buckets are the same. The first time you used http://kowa-nXXXXXX2.oss-cn-xxxxxxx.aliyuncs.com/uploads/news/2018-03-06/AfmJWdArrx.jpg?x-oss-process=image/resize,m_fill,h_60,w_80 to access the object in the destination bucket. The source bucket returns the result of image processing to the destination bucket. The following URLs are the URLs of objects that are stored in the source and destination buckets. The objects are of the same size.

   • Source: http://kowa-nXXXXXX1.oss-cn-xxxxxxx.aliyuncs.com/uploads/news/2018-03-06/AfmJWdArrx.jpg?x-oss-process=image/resize,m_fill,h_60,w_80

   • Destination: http://kowa-nXXXXXX2.oss-cn-xxxxxxx.aliyuncs.com/uploads/news/2018-03-06/AfmJWdArrx.jpg