>> However, sometimes it can create excessive load for cluster in use cases
when there are a lot of thin clients.
Could you please provide some figures? I suppose, that our NIO server can
handle thousands connections easily, and problem
is not in multiple connections.
пт, 25 дек. 2020 г. в 11:33, Pavel Tupitsyn <
[hidden email]>:
> Igor,
>
> The idea is to keep partition awareness enabled
> even when the limit is reached, right?
> So it works when the corresponding server is available,
> and ignored otherwise.
>
> I think this could be useful, but we should document it thoroughly,
> so the negative effect on partition awareness performance is clear.
>
>
> On Fri, Dec 25, 2020 at 12:02 AM Igor Sapego <
[hidden email]> wrote:
>
> > Hi Igniters,
> >
> > As you may know thin clients now can establish connections with
> > multiple servers simultaneously. It is implemented this way to make
> > partition awareness [1] work or for fast failover if partition awareness
> > is not used. However, sometimes it can create excessive load for
> > cluster in use cases when there are a lot of thin clients. I think, we
> > should give user a possibility to limit maximum number of active
> > connections established by a client. What do you think?
> >
> > [1] -
> >
> >
>
https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients> >
> > Best Regards,
> > Igor
> >
>
--
Sincerely yours, Ivan Daschinskiy
Locked
