Re: [jgit-dev] TransportAmazonS3 concurrent push

[Shawn Pearce <spearce@xxxxxxxxxxx>]

On Wed, Oct 2, 2013 at 10:57 AM, James Yonan <james@xxxxxxxxxxx> wrote:
> The docs for TransportAmazonS3 say "Multiple concurrent push operations may
> cause confusion in the repository state."
>
> Is "confusion" just a euphemism for corruption?

Yes. There is no locking, so there is no safe way to ensure your push
doesn't replace someone else's push. Pushes to S3 are essentially
always running with --force. It tries best effort to avoid a
non-fast-forward update, but once its read the value someone else can
replace it without you knowing, and then you replace it, last one
wins. :-)

> If so, any ideas on what would be required to make TransportAmazonS3 safe
> for concurrent pushing?

Locking? Its hard.