From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [Patch 2/2] tabled: rotate the input chunkserver
Date: Fri, 23 Oct 2009 16:40:32 -0400 [thread overview]
Message-ID: <4AE214C0.2050901@garzik.org> (raw)
In-Reply-To: <20091022232602.31374d6d@redhat.com>
On 10/23/2009 01:26 AM, Pete Zaitcev wrote:
> Another step to data redundancy: select the input chunkserver more
> properly than just using the first one. Note: presently, if the
> chunkserver dies while we're accessing it, we do not recover.
> However, application can retry and hit an available one.
>
> Signed-off-by: Pete Zaitcev<zaitcev@redhat.com>
applied 1-2
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?
Jeff
next prev parent reply other threads:[~2009-10-23 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 5:26 [Patch 2/2] tabled: rotate the input chunkserver Pete Zaitcev
2009-10-23 20:40 ` Jeff Garzik [this message]
2009-10-24 2:19 ` Pete Zaitcev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE214C0.2050901@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.