"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 >> >> Jörg >> >> >> >> -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e25a54e0-f392-46c7-bc3a-93a20d6bcbd6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
