Is it really unreasonable that I wish aws would just name their fucking products after what they are? Why the fuck is dns called route 53? Why the fuck is a vm an elastic cloud compute node? Stop being pretentious dicks and just name things what they are!

Am I being unreasonable?

migrated everything to elastic search, shitty learning curve and apparently shittier performance. now i dream of going back

Not sure if it should be a joke or a rant, but something rather funny (at least to me) happened today.

TL;DR; Someone's outlook was crippled by 100k+ of warning notifications

So we have developed a server that has an internal database that wraps around an elastic search instance, that is managed by a POS vault/storage solution, that we have to use for legal reasons. The elastic search is "provided" by the software, but we keep this internal database just to be sure and totally not because it's unreliable POS.

Anyways, they take data integrity very seriously, so every warning our server produces is emailed to someone in charge to review it and if necessary forward it to us. This will be important later on.

Couple of days ago we got error forward when trying to write an entry into the POS software we get an error, because an object we tried to write already existed. After some investigation we concluded an entry was missing when the internal database was created, so we asked them to repopulate elastic search to solve this problem.

When start the server we always sync the internal database to the elastic search and emit a warning when an entry is missing in internal database or vice versa. And well... almost all of them were missing, which caused our server to emit ~40 warnings/ms. Poor outlook. Still investigating for the cause, but damn, I never expected I'd take down someone email account by accident

Go to hell elastic cloud!

While true:
I can’t resize my elasticsearch instance to get memory because it’s stuck….

It’s stuck because it doesn’t has enough memory to actually start …

Wtf!

can you use elastic search as a search engine for your app ?

because i see several weak points in it.

the increased latency after every bulk uploading of docs, meaning u cant ensure fast response time for users

the inability to add synonyms without closing the index ? this is either downtime or ill have to replicate an index to update the original and then switch back to it !!

idk i feel i either must have wrong info or elastic is very inefficient. I might be wrong, not too experienced with it so if I am let me know of some good resources and workarounds that helped you

I started using WordPress in the 1990's - building all kinds of sites that looked OK until all the plugins and new themes came along. As the years have gone by I've become bored with all the tedious little errors and bugs. To the point that I abandoned my print website 10 years ago.
Just tried to edit it today and FUCK NO get me out of here. It's like painting a Rembrandt with a fucking elastic band.

... how the fuck does mutli tenancy work in elastic search / ELK stack, ... isnt there anybody who fucking knows that???

Thoughts on the Elastic stack? I.e. if you have used it and regretted it, please share your horror stories. Or, if you feel that it's great, share why that's the case or how did it help your company/business/product/whatever.