6 ms·
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 re
by freeman478 10y ago
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.
- rdrock 10y agoTrue. 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.
- vacri 10y ago1.5.2 is only 15 months old, which isn't all that long in 'enterprise time'.
- happyslobro 10y agoForget 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.