From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: [Patch 2/2] tabled: rotate the input chunkserver
Date: Fri, 23 Oct 2009 20:19:00 -0600
Message-ID: <20091023201900.373d85fd@redhat.com>
References: <20091022232602.31374d6d@redhat.com>
	<4AE214C0.2050901@garzik.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <hail-devel-owner@vger.kernel.org>
In-Reply-To: <4AE214C0.2050901@garzik.org>
Sender: hail-devel-owner@vger.kernel.org
List-ID: <hail-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>

On Fri, 23 Oct 2009 16:40:32 -0400, Jeff Garzik <jeff@garzik.org> wrote:

> As long as we (a) return an error documented in S3 spec as needing a 
> retry, or (b) close the TCP connection before Content-Length is 
> satisfied, the S3 client should retry, or at least, notice an error and 
> not silently corrupt data.
> 
> Have you verified that (b) occurs, if chunk->tabled->client data 
> pipeline is interrupted after data transfer is under way?

I haven't sorry. Boto by itself doesn't retry, and I don't think
Duplicity does, but I don't know. It's on my "list" to try, but...

-- Pete