Hi,
1. Ignite client node is thread-safe and you can create multiple statements in order to query execution. So, from my point of view, you should close connection when finish all your queries. 2. Could you please clarify your question? 3. I don't think that pooling is required. 4. Ignite client will try to reconnect to the Ignite cluster in case of server node fails. All you need is proper IP finder configuration. On Thu, Nov 10, 2016 at 5:01 PM, Anil <anilk...@gmail.com> wrote: > Any help in understanding below ? > > On 10 November 2016 at 16:31, Anil <anilk...@gmail.com> wrote: > >> I have couple of questions on ignite jdbc connection. Could you please >> clarify ? >> >> 1. Should connection be closed like other jdbc db connection ? - I see >> connection close is shutdown of ignite client node. >> 2. Connection objects are not getting released and all connections are >> busy ? >> 3. Connection pool is really required for ignite client ? i hope one >> ignite connection can handle number of queries in parallel. >> 4. What is the recommended configuration for ignite client to support >> failover ? >> >> Thanks. >> > >
