Class HibernateSearchElasticsearchRuntimeConfigPersistenceUnit.ElasticsearchIndexIndexingConfig
- java.lang.Object
-
- io.quarkus.hibernate.search.orm.elasticsearch.runtime.HibernateSearchElasticsearchRuntimeConfigPersistenceUnit.ElasticsearchIndexIndexingConfig
-
- Enclosing class:
- HibernateSearchElasticsearchRuntimeConfigPersistenceUnit
public static class HibernateSearchElasticsearchRuntimeConfigPersistenceUnit.ElasticsearchIndexIndexingConfig extends Object
-
-
Field Summary
Fields Modifier and Type Field Description (package private) OptionalInt
maxBulkSize
The maximum size of bulk requests created when processing indexing queues.(package private) OptionalInt
queueCount
The number of indexing queues assigned to each index.(package private) OptionalInt
queueSize
The size of indexing queues.
-
Constructor Summary
Constructors Constructor Description ElasticsearchIndexIndexingConfig()
-
-
-
Field Detail
-
queueCount
@ConfigItem(defaultValueDocumentation="10") OptionalInt queueCount
The number of indexing queues assigned to each index.Higher values will lead to more connections being used in parallel, which may lead to higher indexing throughput, but incurs a risk of overloading Elasticsearch, i.e. of overflowing its HTTP request buffers and tripping circuit breakers, leading to Elasticsearch giving up on some request and resulting in indexing failures.
-
queueSize
@ConfigItem(defaultValueDocumentation="1000") OptionalInt queueSize
The size of indexing queues.Lower values may lead to lower memory usage, especially if there are many queues, but values that are too low will reduce the likeliness of reaching the max bulk size and increase the likeliness of application threads blocking because the queue is full, which may lead to lower indexing throughput.
-
maxBulkSize
@ConfigItem(defaultValueDocumentation="100") OptionalInt maxBulkSize
The maximum size of bulk requests created when processing indexing queues.Higher values will lead to more documents being sent in each HTTP request sent to Elasticsearch, which may lead to higher indexing throughput, but incurs a risk of overloading Elasticsearch, i.e. of overflowing its HTTP request buffers and tripping circuit breakers, leading to Elasticsearch giving up on some request and resulting in indexing failures.
Note that raising this number above the queue size has no effect, as bulks cannot include more requests than are contained in the queue.
-
-