Staging instance, all changes can be removed at any time

Skip to content

core/loader: Retry contents loading on HashCollision errors

Here is a simple workaround to avoid HashCollision errors thay may appear when different workers are loading the exact same content in parallel database transactions.

This clearly does not fix the storage issue but at least it should greatly reduce the amount of HashCollision errors reported by the vcs loaders in production.

Related swh-storage#2019 (closed)


Migrated from D2052 (view on Phabricator)

Merge request reports

Loading