We have a development and production offering that uses elasticsearch. In
development, it is not necessary to create many threads and so we're trying
to use as few threads as possible. I've been able to make some great
reductions using the threadpool settings, but there seems to be one that I
can't reduce:
What is the "http_server_worker" threadpool? And is there a way to reduce
how many of them are created? Right now there are 16 of them being created
and I don't think that many will be needed for our purposes.
We have a development and production offering that uses elasticsearch. In
development, it is not necessary to create many threads and so we're trying
to use as few threads as possible. I've been able to make some great
reductions using the threadpool settings, but there seems to be one that I
can't reduce:
What is the "http_server_worker" threadpool? And is there a way to
reduce how many of them are created? Right now there are 16 of them being
created and I don't think that many will be needed for our purposes.
Perfect, that's just what I needed. Is there a comprehensive list of these
properties? I didn't see that property mentioned here:
On Monday, June 23, 2014 5:29:28 PM UTC-5, Jörg Prante wrote:
You can reduce netty workers by transport.netty.worker_count setting
which is by default set to 2 * CPU cores
Jörg
On Mon, Jun 23, 2014 at 10:34 PM, jnortey <jeremy...@gmail.com
<javascript:>> wrote:
We have a development and production offering that uses elasticsearch. In
development, it is not necessary to create many threads and so we're trying
to use as few threads as possible. I've been able to make some great
reductions using the threadpool settings, but there seems to be one that I
can't reduce:
What is the "http_server_worker" threadpool? And is there a way to
reduce how many of them are created? Right now there are 16 of them being
created and I don't think that many will be needed for our purposes.
Hmm, setting transport.netty.worker_count didn't work for me... For the
record, I'm running elasticsearch through the java API, so I don't think
I'm actually using netty. Is there another flag for this property?
On Monday, June 23, 2014 5:29:28 PM UTC-5, Jörg Prante wrote:
You can reduce netty workers by transport.netty.worker_count setting
which is by default set to 2 * CPU cores
"transport.netty.worker_count" is for
"org.elasticsearch.transport.netty.NettyTransport", while
"http_server_works" are started by
"org.elasticsearch.http.netty.NettyHttpServerTransport".
If a class that uses ES's componentSetting is in org.elasticsearch, the
componentSetting takes the part between "org.elasticsearch." and
"ClassName" as prefix.
"NettyHttpServerTransport" settings should start with "http.netty.".
So, try "http.netty.worker_count".
在 2014年6月25日星期三UTC+8上午12时54分32秒,jnortey写道:
Hmm, setting transport.netty.worker_count didn't work for me... For the
record, I'm running elasticsearch through the java API, so I don't think
I'm actually using netty. Is there another flag for this property?
On Monday, June 23, 2014 5:29:28 PM UTC-5, Jörg Prante wrote:
You can reduce netty workers by transport.netty.worker_count setting
which is by default set to 2 * CPU cores
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.