-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Segment Replication] Higher refresh count for segrep enabled indices #7296
Comments
The benchmark comparison for Cluster setup
Steps:
One sample comparison below, baseline: docrep, contender: segrep
|
The root cause here is the same as #7423 (comment). We intentionally disable shard idle with SR enabled indices because replicas cannot independently refresh themselves. The balance here is to bump up refresh interval with SR to slow refresh/merges and write larger segments per refresh cycle at a trade-off of replication lag. |
Closing this issue as we know why this is happening and is expected with lower refresh interval and segrep. Tracking zero replica optimization here. |
As part of benchmarking for Segment replication GA #5147 release, the benchmark results show higher number for backgroud refreshes and merge count (possibly side-effect of first). This difference increases with more data ingestion
Post run completion
Primary shard: ~34gb
Total size: ~70gb
Infra setup
10 m5.xlarge data nodes, 200GB storage, 8 GB JVM
3 cluster manager nodes
The text was updated successfully, but these errors were encountered: