intel-cloud / cosbench

a benchmark tool for cloud object storage service
Other
573 stars 242 forks source link

S3 errors not always logged #334

Closed davidbw closed 6 years ago

davidbw commented 8 years ago

I am doing some cosbench runs to S3 and swift storage and noticed that on some of my tests errors on S3 are not logged properly. To investigate this I created tests to get or put 10 objects to a container that doesn't exist(to force errors) and ran on both S3 and swift.

On the put test: cosbench on swift reports 0% success and workload.log shows all of the errors and reports the error code(404). cosbench on S3 reports 100% success and shows no errors in workload.log.

swift workload.log error output: 2016-10-19 08:28:33,451 [ERROR] [ErrorStatistics] - error code: 404 occurred 11 times, fail to operate: cb-d-c-none-1/test-1, cb-d-c-none-1/test-1, cb-d-c-none-1/test-2, cb-d-c-none-1/test-3, cb-d-c-none-1/test-4, cb-d-c-none-1/test-5, cb-d-c-none-1/test-6, cb-d-c-none-1/test-7, cb-d-c-none-1/test-8, cb-d-c-none-1/test-9, cb-d-c-none-1/test-10

On the get test: cosbench on both swift and S3 find all of the errors and report 0% successs, but on swift workload.log shows the error code(404) while on S3 it says "NA".

swift workload.log output: 016-10-19 08:20:24,213 [ERROR] [ErrorStatistics] - error code: 404 occurred 11 times, fail to operate: cb-d-c-none-1/test-1, cb-d-c-none-1/test-1, cb-d-c-none-1/test-2, cb-d-c-none-1/test-3, cb-d-c-none-1/test-4, cb-d-c-none-1/test-5, cb-d-c-none-1/test-6, cb-d-c-none-1/test-7, cb-d-c-none-1/test-8, cb-d-c-none-1/test-9, cb-d-c-none-1/test-10

S3 workload.log output: 2016-10-18 16:09:01,516 [ERROR] [ErrorStatistics] - error code: N/A occurred 11 times, fail to operate: cb-d-c-none-1/test-1, cb-d-c-none-1/test-1, cb-d-c-none-1/test-2, cb-d-c-none-1/test-3, cb-d-c-none-1/test-4, cb-d-c-none-1/test-5, cb-d-c-none-1/test-6, cb-d-c-none-1/test-7, cb-d-c-none-1/test-8, cb-d-c-none-1/test-9, cb-d-c-none-1/test-10