Elastic and Amazon reach agreement on trademark infringement lawsuit

Re:Elastic and Amazon reach agreement on trademark infringem... by thekevjames on Wednesday February 16, 2022 @07:00PM (#30367615)

FWIW that experience is exactly the same as my team has... But we're on Elastico hosting. Constant black box breakages that can't be debugged, nodes getting restarted for opaque reasons... We've been considering switching to Amazon's hosting to avoid these.

Sounds like it might be a "grass is always greener" scenario. ...maybe I'll spend more time looking into self-hosting...

[ Parent | on HN ]

Re:Elastic and Amazon reach agreement on trademark infringem... by everfrustrated on Wednesday February 16, 2022 @07:12PM (#30367722)

Ditto. Really want to support Elastic but have found their cloud offering just randomly breaks. Latest problem is we lost a node and the new node couldn't recover its shards from backups. Constant crashing until we upsized the instance to have more memory. Makes no sense and support wouldn't lift a finger to help.

[ Parent | on HN ]

Re:Elastic and Amazon reach agreement on trademark infringem... by taf2 on Wednesday February 16, 2022 @08:28PM (#30368464)

Are you running dedicated master nodes? We switched from every node does everything few years ago and it’s been incredibly stable

[ Parent | on HN ]

Re:Elastic and Amazon reach agreement on trademark infringem... by bink on Wednesday February 16, 2022 @09:36PM (#30368900)

I'm surprised they'd even let you run a cluster without dedicated master nodes. It's basic good practice and their docs emphasize this quite clearly.

[ Parent | on HN ]

Re:Elastic and Amazon reach agreement on trademark infringem... by taf2 on Thursday February 17, 2022 @07:16AM (#30372261)

I don’t remember if 12 years ago it was so obvious…. But yes it is very clear these days

[ Parent | on HN ]