That's really weird. There should not be so much connections. Normally thin client will open one TCP connection per node at max. In many cases, there going to be only one connection.
Do you create IgniteClient in your application once, or do you start them several times? Could it be that your code are leaking IgniteClient instances? Can you provide some minimal reproducer to us, so we can debug the issue? Best Regards, Igor On Mon, Mar 25, 2019 at 11:19 PM Brent Williams <brentrw...@gmail.com> wrote: > All, > > I am running Apache Ingite 2.7.0. I have 3 nodes in my cluster, CPU, > memory, GC all tuned properly. I have even adjusted file limit to 65k open > connections. I have 8 client nodes that are connecting to the 3 node > cluster and for the most part working fine, however, we see spikes in > connections and we start to blow out the file limit and we get too many > files open and all client nodes hang. > > When I check the connections per client on one of the server nodes, I am > seeing 5500+ TCP connections established per host. This is roughly 44,0000 > + . My question is what should the file limits be? Why so many TCP > connections per host? How do we control this as it is causing our > production cluster to hang. > > --Brent > > >
