OpenSearch/client
Jason Tedor 31bf279ec7 Tell Netty not to be unsafe in transport client
Today we ship with default jvm.options for server Elasticsearch that
prevents Netty from using some unsafe optimizations. Yet, the settings
do nothing for the transport client since it is embedded in other
applications that will not read and use those settings. This commit adds
these settings for the transport client, and is done so in a way that
still enables users to go unsafe if they want to go unsafe (they
shouldn't, but the option is there).

Relates #22284
2016-12-21 10:49:33 -05:00
..
benchmark Remove `modules/transport_netty_3` in favor of `netty_4` (#21590) 2016-11-17 12:44:42 +01:00
client-benchmark-noop-api-plugin Remove subrequests method from CompositeIndicesRequest (#21873) 2016-11-30 15:03:58 +01:00
rest Don't use null charset in RequestLogger (#22197) 2016-12-15 11:19:51 -05:00
sniffer Upgrade to lucene-6.3.0-snapshot-ed102d6 (#21150) 2016-10-28 14:47:15 +02:00
test Build: Remove old maven deploy support (#20403) 2016-09-19 15:10:41 -07:00
transport Tell Netty not to be unsafe in transport client 2016-12-21 10:49:33 -05:00