Jeff, Does getReadClient() get a reference to a previously created singleton TransportClient (or NodeClient, as the case may be)? I am guessing yes, but just asking to be sure.
In my own set-up, I have created a thin HTTP REST layer (also using Netty, with the LMAX Disruptor to minimize thread usage while maximizing throughput). It contains our business logic, and issues queries and updates to Elasticsearch via the TransportClient. It creates a singleton instance of the TransportClient, and shares this singleton's reference throughout the service. Using seige, I have hammered the combination of my thin server plus Elasticsearch and don't see any performance issues as you describe. Just a thought... Regards, Brian On Monday, December 15, 2014 9:27:18 AM UTC-5, Jeff Potts wrote: > > Yes, updated the gist. Thanks for taking a look at this. > > Jeff > -- 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/e0f039df-95fc-4fb9-a787-84ee56d77e84%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
