Tuning Elasticsearch is an advanced topic, that attending in an Elasticsearch Engineer Training by elastic is pretty simple to understand. The usual answer is always: It depends. I summarise my notes and findings on this. Consider there is always a lot more to it. The training covers it all. It is undoubtedly worth to attend. Education is important ;-). Roughly it is about Elasticsearch Internals (Apache Lucene under the hood), Capacity Planning and smart choices/anticipation.
Add to your ~/.ssh/config the option for every host.
A quick example of JAX-WS with JBoss EAP 7.1.
Index data in Elasticsearch can be easily exported in json encoded text with Logstash.
The aggregations framework helps provide aggregated data based on a search query. Using aggregations on my audit data gives me insight who used my Elasticsearch cluster at what time. This post demonstrates how to translate the Elasticsearch Query DSL into the respective Java Objects of Elastic Java Rest Client.
Elasticsearch with the X-Pack extensions allows you to secure the communication with your Elasticsearch cluster. This post elaborates what actions are needed, to use secure encrypted communication from a Java Rest Client with the encrypted Elasticsearch cluster.
Elasticsearch has common thread defaults for bulk requests. If you need to tune or gap certain problems, you can change the thread and thread pool size settings in elasticsearch.yml. In general it is not recommended to tweak anything! Use it at your own risk!
This post demonstrates the usage of the Cardinality feature.
X-Pack Alerting aka Elasticsearch Watcher can run distributed in a Elasticsearch cluster.