3 ms·
I actually have same conclusion as you. ES isn't easy to tune and run well. A thing many overlook are restart it. You cannot just go and `systemctl restart` it
by kureikain 8y ago
I actually have same conclusion as you. ES isn't easy to tune and run well.
A thing many overlook are restart it. You cannot just go and `systemctl restart` it, once that occurs, constant rebalance happenning because it puts the load to the rest of system and eventually bring them down, all around :(. That make it harder to operator in K8S when it needs time to detach/attach volume, plus the overhead of overlay network.
So I myself didn't know about a perfect tunning. But the log search on Kibana is super helpful though.
That's why I kind of sold on this Loki thing. I have a good feeling that software in Go tend to require less config/tunning compare with Java. Eg, InfluxDB.
> Some other days, you wonder why we moved away from syslog senders and text files...
I wonder the same. I actually like to grep log with tail more than a crappy web ui like Kibana, Sumologic etc.
Tailing log in a webui is clunky.
- styfle 8y ago> once [a reboot] occurs, constant rebalance happening because it puts the load to the rest of system and eventually bring them down, all around I have this same problem with a 3 node cluster, no Kubernetes. This was using Elasticsearch 2.3 and it worked for a year or two and then all of a sudden, any network interruptions would cause the thing to get split brain and all indices would go red. It would take 8+ hours to go back to green and usually required a reboot of all servers or else it would never recover. It was happening often enough that the decision was just run a single ES node since the total data was only 25GB :(