You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We used the connection pool to create and maintain Connections when the database was MySQL, PostgreSQL, and Oracle. As this way, we thought to use pool to manage ESConnection. But when we reviewed code, we found that one ESConnection wrap one TransportClient instance. If we use the pool, there will be multiple TransportClient instances in project (one JVM). However, official suggests that one client in one JVM.
So what should we do? Use only one ESConnection instance or multiple ESConnection instances in a pool? thanks for your reply?
The text was updated successfully, but these errors were encountered:
From the running of test cases against Elasticsearch 6.4.0, one ESConnection may spawn quite a number of threads by Elasticsearch which is using Apache Async HttpClient by default. Do take note if you want to use more than one connection.
We used the connection pool to create and maintain Connections when the database was MySQL, PostgreSQL, and Oracle. As this way, we thought to use pool to manage ESConnection. But when we reviewed code, we found that one ESConnection wrap one TransportClient instance. If we use the pool, there will be multiple TransportClient instances in project (one JVM). However, official suggests that one client in one JVM.
So what should we do? Use only one ESConnection instance or multiple ESConnection instances in a pool? thanks for your reply?
The text was updated successfully, but these errors were encountered: