Igor, > not clear how a server would know when assignment has changed
On the server, TableManager [1] maintains the current assignment. I've made some changes there (see the linked POC) to subscribe to those updates. However, as I understand, this logic is not yet complete and will be changed soon. In any case, the server should maintain up-to-date assignment one way or another, because server-side API needs to route requests as well. [1] https://github.com/apache/ignite-3/pull/1080/files#diff-8539b597e51096e7007250e746e696d4e16351d09c3756b4989a1c331f788ead On Thu, Sep 15, 2022 at 10:29 AM Igor Sapego <isap...@apache.org> wrote: > Pavel, > > Great, this feature showed great results in Ignite 2, so It's a good idea > to implement > it in Ignite 3 as well. > > The IEP itself looks good to me, except it's not clear how a server would > know when > assignment has changed. > > Regardless of the Tracking Assignment Changes section, I like the first > approach > the best. Yeah, idle clients do not get updates, but why would idle clients > need > assignment update anyway if they are idle? > > Best Regards, > Igor > > > On Thu, Sep 15, 2022 at 11:21 AM Pavel Tupitsyn <ptupit...@apache.org> > wrote: > > > Igniters, > > > > Please review the IEP for client partition awareness in Ignite 3 and let > me > > know what you think. > > > > [1] > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-95+Client+Partition+Awareness > > [2] https://github.com/apache/ignite-3/pull/1080 > > >
