Things learned using Elastic Search (2013)
sammaye.wordpress.com
sammaye.wordpress.com
- Making daily backups with S3.
- Having a replica physical cluster (note, not a replica node). Because replica nodes can corrupt each other.
- Forget about rivers. Implement your own. What I did was push row ids into a Redis list, and when the list becomes filled with 100 IDs, I query all 100 items from my database, and index them into ElasticSearch. Nothing complicated.
This definitely feels like a rant that picks up on a few issues with ES, and then smothers it with a variety of things which are different, but not really "issues". I've found the ES documentation to be a bit fragmented, but good once you know where things are. It's not the most newbie friendly system, but once you're up and running it's incredibly powerful.
Well, get with the times ffs.
Amuzingly, I recently integrated ES with a Yii app and it ran wonderfully. Sped up our search considerably.
Some of these points aren't too important, like having to use composer (you don't ever have to use composer, by the way). The library file size I'm also not too concerned about.
Result speed and the terrible docs are interesting, however.
They acknowledge this themselves as well, that's why they released a book that should help first time users to navigate through ES: http://www.elasticsearch.org/blog/elasticsearch-definitive-g...