High number of "I/O dispatcher" threads using log4j2-elasticsearch-jest about log4j2-elasticsearch HOT 7 CLOSED

@JeromeSoussens Good point!
The only workaround atm is to extend JestHttpObjectFactory(log4j2-elasticsearch-jest), JestClientFactory(jest) and HttpClientConfig(jest).

IOReactorConfig.setIOThreadCount(int) allows to configure it and set it at AbstractMultiworkerIOReactor:157, so I'll just expose it via ioThreadCount attribute at JestHttp and JestBufferedHttp in 1.3.1 (I'm planning on releasing it soon).

Great find! Thank you! 👍

from log4j2-elasticsearch.

Hi @rfoltyns ,
Thanks for your reply, that would be great to be able to configure the ioThreadCount !

from log4j2-elasticsearch.

Hi @rfoltyns ,
What are your plans regarding the fix for this issue ? Will it be in the next release ?

Thanks

from log4j2-elasticsearch.

@JeromeSoussens I had to shift the priorities a bit due to more and more issues related with Spring Boot startup. I had to patch it asap.
I''ve planned to work on ioThreadCount this week though.. along with the extension of lifecycle integration to JestHttpClient. Hoping to fix another Spring Boot "quirk" - even though ioThreadCount is, e.g.: 8, actual number of IO threads is 16 cause the client starts twice!
Lifecycle extension and ioThreadCount config WILL be released in 1.3.2 (first half of February)

from log4j2-elasticsearch.

Released in 1.3.2
Enjoy! :)

from log4j2-elasticsearch.

Thank you very much !
It works like a charm.

from log4j2-elasticsearch.

Glad to help! Thanks again for this.
If you have any other suggestions regarding useful config options, feel free to open more issues or PRs.

BTW, I've found that shrinking IO threads too low can choke the client easily on higher workloads, so use with caution ;)

from log4j2-elasticsearch.