Gateway ST and Gateway MT are different?

Does Gateway ST and Gateway MT behave different.

Due to I tred to setup a QNAP internal HBS§ backup job. With Gateway MT it works like a charm with self hosted Gateway ST version 1.2.0 via docker it works also with small amount of data.

When I increase the backup data e.g. to 1.25 GB it never end the backup. I see then a lot of messages in the Gateway ST logs

2021-08-03T11:12:24.147Z INFO ecclient Upload to node canceled by user {“Node ID”: “1UXJaq3XfBpgwBkLiFxBvtAdusWY5FoHG4r1fo7jcmxygMKnU”}
2021-08-03T11:12:24.148Z INFO ecclient Upload to node canceled by user {“Node ID”: “142k8NaRwiKi2dWUgdf4HS56E8AnYr88BChDgC1gDuEdJWfeYy”}
2021-08-03T11:12:24.148Z INFO ecclient Upload to node canceled by user {“Node ID”: “12pNbFFj7G6Y5C9dgzRe5GtA1cb8ucQSeH6qpoTstKwCJm2GnR5”}

Those lines look like just longtail cancellation, but I could be wrong. That’s normal behavior when enough pieces are uploaded.

According to one of our gateway engineers, Gateway-ST and Gateway-MT have diverged significantly over time, with Gateway-MT receiving significantly more attention. Currently there is an effort to more closely unify them moving forward. Both are currently based on Minio for S3 support, but at the moment they reference different versions of Minio. We hope to unify the two as much as possible over the next 2-8 weeks; as much as possible using the more permissive Apache2 license (Minio recently changed their license to AGPL).
In the mean time, perhaps multipart POSTs instead of PUTs would fix address timeout issue?

3 Likes

What does this mean ?

Those would be features of the S3 API. Since you’re using a QNAP backup solution, see if there is an option to turn on multipart. Preferably with a part size of 64MB.

3 Likes

I can not found such kind of option.

Have sombody else ever bring it up to work?