Scale Elasticsearch for Your Java Applications. Philipp Krenn. Java Fest 2020 Online
summary
Shows a small Java injector that uses the Elasticsearch high‑level REST client and proves concrete wins: switching from single-document HTTP calls to bulk requests cuts 1,000 inserts from ~49s to ~11s (and can reach ~4s with tuning). Demonstrates changing the refresh interval for large imports, why default sharding moved to one primary+one replica, shard sizing guidance (avoid tiny shards, aim >10–50GB, limit shards per GB of heap), and replacing deep pagination with search_after or scroll. Uses Kibana monitoring and Rally for benchmarks.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:12for Your Java Applications
- 1:38Terminology Cluster, Node, Index, Shard
- 5:02Disclaimer This is not a benchmark
- 13:40Stack Monitoring
- 20:43Optimal Bulk Size?
- 22:37index.refresh_interval Default is
- 28:08Load Distribution
- 30:27Topology Sniffing Cloud Proxy
- 31:18Distribution Round Robin Adaptive Replica Selection for searches
- 33:34Index Patterns Static vs Time-Based
- 39:23Pagination
- 42:37For Your Protection index.max_result_window: 10000
- 47:23Rally Macrobenchmarking Framework for Elasticsearch
- 48:02Nightly Benchmarks
related talks
54mAdvanced (elastic)search for your legacy application
47mAdvanced (Elastic) Search for Your Legacy Application
01h 01mBest Practices With Elasticsearch
16mSo many results... Give them to me!
29mHow (not) to Scale Elasticsearch for Data Analytics!
51mAdvanced search for your legacy application
35mElasticsearch - Beyond Full-text Search
01h 00mAdvanced search for your legacy application
