Igniters, Are we moving forward with this release? Alex Plehanov, are you still ready to manage it? It seems like everyone agreed with the timeline you proposed in the very beginning.
- Denis On Tue, Jun 16, 2020 at 8:52 AM Denis Magda <dma...@apache.org> wrote: > Sergey, Ivan, > > Could you please check the questions below? If it's time-consuming to > rework continuous queries, then the new mode can become available in the > experimental state and should not let register continuous queries to avoid > potential deadlocks. Overall, this design gap in continuous queries was > like a bomb that has just detonated [1]. Anyway, this new connectivity mode > will be priceless even if you can't use continuous queries with them > because right now we cannot even start a thick client inside of a > serverless function. > > Alexey Plehanov, > > It looks like we can proceed with the release taking your timelines. > > [1] https://issues.apache.org/jira/browse/IGNITE-13156 > > - > Denis > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <dma...@apache.org> wrote: > >> Ivan, Sergey, >> >> How much effort should we put to resolve the issue with >> continuous queries? Are you working on that issue actively? Let's try to >> guess what would be the ETA. >> >> - >> Denis >> >> >> On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov <bessonov...@gmail.com> >> wrote: >> >>> Hello, >>> >>> Sorry for the delay. Sergey Chugunov (sergey.chugu...@gmail.com) just >>> replied >>> to the main conversation about "communication via discovery" [1]. We >>> work on it >>> together and recently have found one hard-to-fix scenario, detailed >>> description is >>> provided in Sergey's reply. >>> >>> In short, July 10th looks realistic only if we introduce new behavior in >>> its current >>> implementation, with new setting and IgniteExperimental status. Blocker >>> here is >>> current implementation of Continuos Query protocol that in some cases >>> (described >>> at the end) initiates TCP connection right from discovery thread which >>> obviously >>> leads to deadlock. We haven't estimated efforts needed to redesign of CQ >>> protocol >>> but it is definitely a risk and fixing it isn't feasible with a code >>> freeze at 10th of July. >>> So my verdict: we can include this new feature in 2.9 scope as >>> experimental and with >>> highlighted limitation on CQ usage. Is that OK? >>> >>> CQ limitation: server needs to open a communication connection to the >>> client if during >>> CQ registration client tries to p2p deploy new class not available on >>> server classpath. >>> In other cases registration of CQ should be fine. >>> >>> [1] >>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html >>> >>> вт, 9 июн. 2020 г. в 19:36, Ivan Rakov <ivan.glu...@gmail.com>: >>> >>>> Hi, >>>> >>>> Indeed, the tracing feature is almost ready. Discovery, communication >>>> and >>>> transactions tracing will be introduced, as well as an option to >>>> configure >>>> tracing in runtime. Right now we are working on final performance >>>> optimizations, but it's very likely that we'll complete this activity >>>> before the code freeze date. >>>> Let's include tracing to the 2.9 release scope. >>>> >>>> More info: >>>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing >>>> https://issues.apache.org/jira/browse/IGNITE-13060 >>>> >>>> -- >>>> Best Regards, >>>> Ivan Rakov >>>> >>>> On Sat, Jun 6, 2020 at 4:30 PM Denis Magda <dma...@apache.org> wrote: >>>> >>>> > Hi folks, >>>> > >>>> > The timelines proposed by Alex Plekhanov sounds reasonable to me. I'd >>>> like >>>> > only to hear inputs of @Ivan Rakov <ira...@gridgain.com>, who is >>>> about to >>>> > finish with the tracing support, and @Ivan Bessonov >>>> > <ibesso...@gridgain.com>, who is fixing a serious limitation for K8 >>>> > deployments [1]. Most likely, both features will be ready by the code >>>> > freeze date (July 10), but the guys should know it better. >>>> > >>>> > [1] >>>> > >>>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-New-Ignite-settings-for-IGNITE-12438-and-IGNITE-13013-td47586.html >>>> > >>>> > - >>>> > Denis >>>> > >>>> > >>>> > On Wed, Jun 3, 2020 at 4:45 AM Alex Plehanov <plehanov.a...@gmail.com >>>> > >>>> > wrote: >>>> > >>>> >> Hello Igniters, >>>> >> >>>> >> AI 2.8.1 is finally released and as we discussed here [1] its time to >>>> >> start >>>> >> the discussion about 2.9 release. >>>> >> >>>> >> I want to propose myself to be the release manager of the 2.9 >>>> release. >>>> >> >>>> >> What about release time, I agree with Maxim that we should deliver >>>> >> features >>>> >> as frequently as possible. If some feature doesn't fit into release >>>> dates >>>> >> we should better include it into the next release and schedule the >>>> next >>>> >> release earlier then postpone the current release. >>>> >> >>>> >> I propose the following dates for 2.9 release: >>>> >> >>>> >> Scope Freeze: June 26, 2020 >>>> >> Code Freeze: July 10, 2020 >>>> >> Voting Date: July 31, 2020 >>>> >> Release Date: August 7, 2019 >>>> >> >>>> >> WDYT? >>>> >> >>>> >> [1] : >>>> >> >>>> >> >>>> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Releases-Plan-td47360.html#a47575 >>>> >> >>>> > >>>> >>> >>> >>> -- >>> Sincerely yours, >>> Ivan Bessonov >>> >>
