1. We changed a configuration parameter, which we thought would be a no-op but c... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

lflux on Oct 11, 2019 | parent | context | favorite | on: AWS Elasticsearch: a fundamentally-flawed offering

1. We changed a configuration parameter, which we thought would be a no-op but caused a deploy

2. We ran a fairly large cluster with a large amount of i3.xlarge

3. One AZ in us-west-1 didn't have enough capacity of that SKU . The other AZ did, but this doesn't help if you have a multi-AZ deployment.

4. We switched to EBS-based instances after this

nostrebored on Oct 11, 2019 [–]

Reach out to your TAM again to talk about CR and RI combinations which can help to mitigate this problem.

lflux on Oct 11, 2019 | [–]

Migrating to a different hosting platform than AWS for ES aslo mitigates this problem too, which is more likely in our case.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact