It looks like from implementation point of view fastjson parser pool doesn't behave the same way as expected when dealing many `xl.json` from multiple disks. The fastjson parser pool usage ends up returning incorrect xl.json entries for checksums, with references pointing to older entries. This led to the subtle bug where checksum info is duplicated from a previous xl.json read of a different file from different disk. |
||
---|---|---|
.. | ||
gateway-s3-metadata.go | ||
gateway-s3-metadata_test.go | ||
gateway-s3-sse.go | ||
gateway-s3-utils.go | ||
gateway-s3.go | ||
gateway-s3_test.go |