[
https://issues.apache.org/jira/browse/OAK-11545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nuno Santos updated OAK-11545:
------------------------------
Fix Version/s: 1.80.0
> oak-search-elastic: implement bulk processor pool to optimize indexing
> ----------------------------------------------------------------------
>
> Key: OAK-11545
> URL: https://issues.apache.org/jira/browse/OAK-11545
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-search-elastic
> Reporter: Nuno Santos
> Priority: Minor
> Fix For: 1.80.0
>
>
> We are currently creating/destroying a BulkProcessor instance every time an
> ElasticsearchIndexWriter gets created/closed.
> Besides this, ElasticsearchIndexWriter get created for every elastic index.
> So If an instance has 5 different elastic indices, then 5 instances of bulk
> processor will be created for every async run for that lane.
> We can be a lot smarter re-using BulkProcessor(s) among different indexes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
