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@xxxxxxxxxx>
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
--
To unsubscribe from this list: send the line "unsubscribe hail-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
