I've been writing the ES/EC2 tutorial that Clinton put me up to.
I would like to include some content about the downsides of using the S3
I suppose performance isn't an issue since ES will write asynchronously. I
know the performance of a recovery is slower because of the EC2/S3 IO
As I see it, there must be some kind of potential consistency problem since
ES writes to the S3 gateway asynchronously. If the asynchronous write fails
because of an abrupt termination of a cluster node, isn't is possible that
the gateway will be in an inconsistent state? I suppose that some other node
will be the destination of the failed primary shard and could potentially
correct the problem. If the primary and replica nodes for a shard all fail,
couldn't the gateway get out of sync?
If yes, can the gateway be corrupted, or will it just recover to a prior