_________________________________________________________________________
- Upgrading to the new major version right after its release without waiting for the inevitable .1 release
- Remembering that you said, “We don’t need backups, we have shard replicas” to your manager during an 8-hour cluster recovery session
- Not running dedicated masters and wondering why your whole cluster becomes unresponsive during high load
- In a room full of Elasticsearch fans suggest that Elasticsearch should use ZooKeeper like SolrCloud and avoid split-brain
- Running a single master and wondering why it takes the whole cluster down with it
- Running a significant terms aggregation on an analyzed field and wondering where all the memory/heap went
- Not using G1 GC with large heaps because Robert Muir claims G1 and Lucene/Elasticsearch don’t get along (just kidding, Robert!)
- Giving Elasticsearch JVM 32 GB heap and thinking you’re so clever ‘cause you’re still using CompressedOops. Tip: you ain’t
- Restarting multiple nodes too fast without waiting for the cluster to go green between node restarts
- …and last but not least: not taking Sematext Elasticsearch guru @radu0gheorghe’s upcoming Elasticsearch / ELK Stack Training course in October in NYC! [Note: since this workshop has already taken place, stay up to date with future workshops at our Elasticsearch training page]
Filed under: Search Tagged: elasticsearch
