You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Appender creates bulkIndexers at runtime when the Appender is created. Instead of doing that, we could pass in a BulkIndexerPool, which contains a bounded pool of bulkIndexers and could be shared by multiple Appender instances to create a maximum memory boundary.
For fairness across different go-docappender instances, it would be good also to implement a per-go-docappender limit so one appended isn't potentially consuming all the bulk indexers.
The text was updated successfully, but these errors were encountered:
Currently, the
Appender
createsbulkIndexer
s at runtime when the Appender is created. Instead of doing that, we could pass in aBulkIndexerPool
, which contains a bounded pool ofbulkIndexer
s and could be shared by multipleAppender
instances to create a maximum memory boundary.For fairness across different
go-docappender
instances, it would be good also to implement a per-go-docappender limit so one appended isn't potentially consuming all the bulk indexers.The text was updated successfully, but these errors were encountered: