AWS Elasticsearch Service Woes

Re:AWS Elasticsearch Service Woes by freeman478 on Monday June 27, 2016 @07:56AM (#11985567)

The main issue of this service is just that it is very outdated (it only supports ES 1.5.2) when the latest is 2.3.3 and ES 5 is just around the corner.

The recent versions are far more stable and includes lots of efficiency in terms of memory usage.

[ Parent | on HN ]

Re:AWS Elasticsearch Service Woes by vacri on Monday June 27, 2016 @10:11AM (#11986220)

1.5.2 is only 15 months old, which isn't all that long in 'enterprise time'.

[ Parent | on HN ]

Re:AWS Elasticsearch Service Woes by happyslobro on Monday June 27, 2016 @01:18PM (#11987663)

Forget enterprise time, it's about to be two major versions old in major version time, once v5 is official. Not sure what happened to v3 and v4, I think Elastic skipped them to get all of their products aligned to the same version.

Elastic says they don't backport fixes either, so in this case, it might be a good idea to stay near the leading edge of the release cycle.

[ Parent | on HN ]

Re:AWS Elasticsearch Service Woes by rdrock on Monday June 27, 2016 @08:04AM (#11985601)

True. As much as a service entices us, old version and having no timeframe of when we can expect an update to a newer version made us keep our self-managed cluster on EC2.

[ Parent | on HN ]