Denis, Folks, It the link correct? https://blogs.apache.org/ignite/entry/ignite-2-8-released-less
I can't get access to it. Can anyone else confirm that everything is OK? On Wed, 11 Mar 2020 at 23:52, Denis Magda <dma...@apache.org> wrote: > > Folks, > > I've published the blog post: > https://blogs.apache.org/ignite/entry/ignite-2-8-released-less > > @Maxim Muzafarov, please proceed with an announcement email including a > reference to the blog for those who'd like to find out details. > > - > Denis > > > On Wed, Mar 11, 2020 at 1:17 AM Anton Vinogradov <a...@apache.org> wrote: >> >> >> Does it mean that the PME is skipped only for cases when the native >> >> persistence is used and a failed node was in the baseline topology? >> The cluster should be fully rebalanced (late affinity assignment happened) >> and the failed node should be from the baseline topology. >> Otherwise, you'll gain regular (PME based) switch. >> >> >> How about pure in-memory clusters and clusters with CacheStore? >> Such configuration leads to partitions reassignment in case of node left. >> This means we have to relocate primaries and backups once they will be >> rebalanced. >> This leads to subsequent LAA PME (after Left switch). >> Initial PME is required to calculate and apply new affinity and perform >> preparations for LAA. >> >> On Tue, Mar 10, 2020 at 7:25 PM Denis Magda <dma...@apache.org> wrote: >> >> > Anton, >> > >> > Does it mean that the PME is skipped only for cases when the native >> > persistence is used and a failed node was in the baseline topology? How >> > about pure in-memory clusters and clusters with CacheStore? >> > >> > - >> > Denis >> > >> > >> > On Tue, Mar 10, 2020 at 12:40 AM Anton Vinogradov <a...@apache.org> wrote: >> > >> > > Denis, >> > > >> > > >> the blocking PME no longer happens if a node leaves the cluster >> > > We should mention this should be the baseline node >> > > >> > > On Tue, Mar 10, 2020 at 9:40 AM Denis Magda <dma...@apache.org> wrote: >> > > >> > > > Pavel, thank you. I referred to your article from a blog post to be >> > > > published on blogs.apache.org. Please feel free to share feedback >> > before >> > > > it's published. You can use the comment feature of Google Docs: >> > > > >> > > > >> > > >> > https://docs.google.com/document/d/1ssTC1Jf_reqZFWgl4ayhaohiAJCpzdL4tPrHTxvfvAM/edit?usp=sharing >> > > > >> > > > >> > > > @Alexey Zinoviev <zaleslaw....@gmail.com> , @Andrey Gura >> > > > <ag...@apache.org> , @Nikolay Izhikov <nizhi...@apache.org>, @Anton >> > > > Vinogradov <a...@apache.org> could you glance at the paragraphs >> > > mentioning >> > > > the improvements you contributed to the release? I just want to be sure >> > > my >> > > > understanding is correct. >> > > > >> > > > - >> > > > Denis >> > > > >> > > > >> > > > On Mon, Mar 9, 2020 at 3:54 AM Pavel Tupitsyn <ptupit...@apache.org> >> > > > wrote: >> > > > >> > > >> Published: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.8/ >> > > >> >> > > >> On Sat, Mar 7, 2020 at 1:49 AM Pavel Tupitsyn <ptupit...@apache.org> >> > > >> wrote: >> > > >> >> > > >> > Denis, ok, I'll publish on Monday afternoon then (UTC), weekend is >> > not >> > > >> the >> > > >> > best time. >> > > >> > >> > > >> > Thanks, >> > > >> > Pavel >> > > >> > >> > > >> > On Sat, Mar 7, 2020 at 1:25 AM Denis Magda <dma...@apache.org> >> > wrote: >> > > >> > >> > > >> >> Pavel, >> > > >> >> >> > > >> >> Thanks for clarifying the way partition-awareness handles topology >> > > >> >> changes. >> > > >> >> >> > > >> >> Please publish your article as soon as you're ready. I plan to >> > finish >> > > >> mine >> > > >> >> on Monday-Tuesday and will refer to yours. >> > > >> >> >> > > >> >> - >> > > >> >> Denis >> > > >> >> >> > > >> >> >> > > >> >> On Fri, Mar 6, 2020 at 1:36 AM Pavel Tupitsyn < >> > ptupit...@apache.org> >> > > >> >> wrote: >> > > >> >> >> > > >> >> > Denis, thanks for the feedback! >> > > >> >> > When should I publish the post? Right after official release >> > > >> >> announcement, >> > > >> >> > or later? >> > > >> >> > >> > > >> >> > > I would use "thick client" as a term instead of the "classic >> > > >> client" >> > > >> >> > Good point, fixed >> > > >> >> > >> > > >> >> > > partition-awareness doesn't handle topology changes >> > automatically >> > > >> >> > (partition map won't be updated on the client-side) >> > > >> >> > This is not true, we keep the partition map up to date by >> > checking >> > > >> >> > AffinityTopologyVersion [1] >> > > >> >> > >> > > >> >> > > Now I can run Ignite.NET easily on my Mac OS machine >> > > >> >> > Just to clarify, you can do that since 2.4 release [2]. >> > > >> >> > In 2.8 we have refined build-related things (jar file handling), >> > > and >> > > >> >> made >> > > >> >> > sure that recent .NET versions are supported. >> > > >> >> > >> > > >> >> > [1] >> > > >> >> > >> > > >> >> > >> > > >> >> >> > > >> >> > > >> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients >> > > >> >> > [2] https://habr.com/ru/company/gridgain/blog/347374/ (in >> > Russian) >> > > >> >> > >> > > >> >> > On Fri, Mar 6, 2020 at 2:40 AM Denis Magda <dma...@apache.org> >> > > >> wrote: >> > > >> >> > >> > > >> >> > > Pavel, thanks, >> > > >> >> > > >> > > >> >> > > I enjoyed reading the blog, crystal clear and straight to the >> > > >> point! >> > > >> >> > Please >> > > >> >> > > consider these several items that might strengthen the article >> > a >> > > >> bit: >> > > >> >> > > >> > > >> >> > > - I would use "thick client" as a term instead of the >> > "classic >> > > >> >> client" >> > > >> >> > > (and mention that Ignite.NET client is a thick one). The >> > thick >> > > >> >> client >> > > >> >> > is >> > > >> >> > > already a coined term that based on my observations are >> > used a >> > > >> lot >> > > >> >> by >> > > >> >> > > dev >> > > >> >> > > and user communities. Also, you might add some differences >> > of >> > > >> thick >> > > >> >> > vs. >> > > >> >> > > thin taking from this page - >> > > >> >> > > >> > > >> >> > > >> > > >> >> > >> > > >> >> >> > > >> >> > > >> > https://www.gridgain.com/docs/latest/installation-guide/deployment-modes#thick-vs-thin-clients >> > > >> >> > > - Should we mention that presently partition-awareness >> > doesn't >> > > >> >> handle >> > > >> >> > > topology changes automatically (partition map won't be >> > updated >> > > >> on >> > > >> >> the >> > > >> >> > > client-side)? This might be a blocker for some users. >> > > >> >> > > - Excited to read about the cross-platform support, that's >> > > huge! >> > > >> >> Now I >> > > >> >> > > can run Ignite.NET easily on my Mac OS machine. I would >> > > insert a >> > > >> >> > > reference >> > > >> >> > > to updated documentation pages that explain how to start >> > with >> > > >> >> > > Ignite.NET on >> > > >> >> > > various platforms. >> > > >> >> > > >> > > >> >> > > Hope, you will find this helpful, thanks for helping with >> > project >> > > >> >> > > promotion! >> > > >> >> > > >> > > >> >> > > - >> > > >> >> > > Denis >> > > >> >> > > >> > > >> >> > > >> > > >> >> > > On Thu, Mar 5, 2020 at 7:32 AM Pavel Tupitsyn < >> > > >> ptupit...@apache.org> >> > > >> >> > > wrote: >> > > >> >> > > >> > > >> >> > > > Denis, >> > > >> >> > > > >> > > >> >> > > > The first post is going to be ready soon, probably by >> > tomorrow. >> > > >> >> > > > Here is a draft, feedback welcome: >> > > >> >> > > > >> > > >> >> > > > >> > > >> >> > > >> > > >> >> > >> > > >> >> >> > > >> >> > > >> > https://github.com/ptupitsyn/ptupitsyn.github.io/blob/ignite-2.8/_posts/2020-03-05-Whats-New-In-Ignite-Net-2.8.md >> > > >> >> > > > >> > > >> >> > > > On Wed, Mar 4, 2020 at 5:15 PM Denis Magda < >> > dma...@apache.org> >> > > >> >> wrote: >> > > >> >> > > > >> > > >> >> > > > > Hi Pavel, >> > > >> >> > > > > >> > > >> >> > > > > Excellent! It will be good to publish the first article >> > > (what's >> > > >> >> new >> > > >> >> > in >> > > >> >> > > > > Ignite.NET 2.8) prior to a generic blog on >> > blogs.apache.org >> > > so >> > > >> >> that >> > > >> >> > we >> > > >> >> > > > can >> > > >> >> > > > > link your post in for those who are looking for more >> > details. >> > > >> Do >> > > >> >> you >> > > >> >> > > have >> > > >> >> > > > > any timeline in mind for this article? >> > > >> >> > > > > >> > > >> >> > > > > @Alexey Zinoviev <zaleslaw....@gmail.com>, how about you >> > > >> >> preparing >> > > >> >> > > > several >> > > >> >> > > > > paragraphs for the blog highlighting the biggest changes in >> > > ML? >> > > >> >> The >> > > >> >> > > same >> > > >> >> > > > > highlighted content will be elaborated during the webinar. >> > > >> >> > > > > >> > > >> >> > > > > - >> > > >> >> > > > > Denis >> > > >> >> > > > > >> > > >> >> > > > > >> > > >> >> > > > > On Wed, Mar 4, 2020 at 2:29 AM Pavel Tupitsyn < >> > > >> >> ptupit...@apache.org> >> > > >> >> > > > > wrote: >> > > >> >> > > > > >> > > >> >> > > > > > Denis, I have a few blog posts on Ignite.NET planned: >> > > >> >> > > > > > >> > > >> >> > > > > > * What's new in Ignite.NET 2.8 (Thin Client Partition >> > > >> Awareness, >> > > >> >> > > > logging, >> > > >> >> > > > > > expiry policy, cluster API, .NET Core 3.x, Dockerfile) >> > > >> >> > > > > > * Ignite.NET performance improvements on .NET Core 3.x >> > > >> >> > > > > > * Ignite.NET Partition Awareness performance >> > > >> >> > > > > > * Fixing JNI thread leak in Ignite.NET >> > > >> >> > > > > > >> > > >> >> > > > > > What do you think? Should we have a schedule of some >> > sorts? >> > > >> >> > > > > > >> > > >> >> > > > > > On Tue, Mar 3, 2020 at 9:58 PM Alexey Zinoviev < >> > > >> >> > > zaleslaw....@gmail.com >> > > >> >> > > > > >> > > >> >> > > > > > wrote: >> > > >> >> > > > > > >> > > >> >> > > > > > > Sounds ineresting, will help with the post, please >> > share >> > > >> the >> > > >> >> > > > template, >> > > >> >> > > > > > not >> > > >> >> > > > > > > sure about webinar >> > > >> >> > > > > > > >> > > >> >> > > > > > > вт, 3 мар. 2020 г., 20:59 Denis Magda < >> > dma...@apache.org >> > > >: >> > > >> >> > > > > > > >> > > >> >> > > > > > > > Igniters, >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > Let's discuss approaches for a global >> > > >> >> announcement/promotion of >> > > >> >> > > the >> > > >> >> > > > > > > > release. I would suggest focusing on a blog post and >> > a >> > > >> >> > community >> > > >> >> > > > > > webinar. >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > The blog post will introduce significant improvements >> > > >> >> (service >> > > >> >> > > > grid, >> > > >> >> > > > > > thin >> > > >> >> > > > > > > > clients, new metrics system, ML, etc.) sharing >> > > >> references to >> > > >> >> > > > > > > documentation >> > > >> >> > > > > > > > pages with more details. It will be published on >> > > >> >> > > blogs.apache.org >> > > >> >> > > > > in >> > > >> >> > > > > > a >> > > >> >> > > > > > > > format similar to this one - >> > > >> >> > > > > > > > >> > > >> >> https://blogs.apache.org/ignite/entry/apache-ignite-2-7-deep. >> > > >> >> > I >> > > >> >> > > > can >> > > >> >> > > > > > work >> > > >> >> > > > > > > > on >> > > >> >> > > > > > > > it unless anybody else is willing to share the news >> > on >> > > >> >> behalf >> > > >> >> > of >> > > >> >> > > > the >> > > >> >> > > > > > > > community. >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > Next, the blog post will be featuring a community >> > > webinar >> > > >> >> that >> > > >> >> > is >> > > >> >> > > > > > > breaking >> > > >> >> > > > > > > > down a subset of the improvements in more detail. >> > > Please >> > > >> >> see an >> > > >> >> > > > > > abstract >> > > >> >> > > > > > > > below with suggested topics for a detailed overview. >> > > >> @Alexey >> > > >> >> > > > Zinoviev >> > > >> >> > > > > > > > <zaleslaw....@gmail.com>, would you be able to >> > present >> > > >> the >> > > >> >> ML >> > > >> >> > > > part? >> > > >> >> > > > > > > > @Nikolay >> > > >> >> > > > > > > > Izhikov <nizhi...@apache.org> or @Andrey Gura < >> > > >> >> > > ag...@gridgain.com> >> > > >> >> > > > > > would >> > > >> >> > > > > > > > you like to take over the metrics section? I'll work >> > > the >> > > >> >> > > attendees >> > > >> >> > > > > > > through >> > > >> >> > > > > > > > the items listed in "Sustainable production under >> > high >> > > >> >> load". >> > > >> >> > We >> > > >> >> > > > > should >> > > >> >> > > > > > > > target the webinar for the April timeframe. >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > *Topmost changes in Apache Ignite 2.8 for production >> > > >> >> > maintenance >> > > >> >> > > > and >> > > >> >> > > > > > > > machine learning* >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > *Apache Ignite community rolled out more than 1900 >> > > >> changes >> > > >> >> in >> > > >> >> > > > Ignite >> > > >> >> > > > > > 2.8 >> > > >> >> > > > > > > > that enhanced almost all the components of the >> > > platform. >> > > >> The >> > > >> >> > > > release >> > > >> >> > > > > > > notes >> > > >> >> > > > > > > > go with hundreds of lines trying to catalog the >> > > >> >> improvements. >> > > >> >> > > Join >> > > >> >> > > > > this >> > > >> >> > > > > > > > webinar led by Ignite community members demonstrating >> > > and >> > > >> >> > > > dissecting >> > > >> >> > > > > > new >> > > >> >> > > > > > > > capabilities related to production maintenance, >> > > >> monitoring, >> > > >> >> and >> > > >> >> > > > > machine >> > > >> >> > > > > > > > learning that you do not want to lose sight of:* >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > - *Sustainable production under high load: Ignite >> > > >> >> > persistence >> > > >> >> > > > > > > compaction >> > > >> >> > > > > > > > and consistent crash recovery, baseline topology >> > > >> >> > > > auto-adjustment, >> > > >> >> > > > > no >> > > >> >> > > > > > > > interruption of operations for some cluster >> > topology >> > > >> >> change >> > > >> >> > > > > events.* >> > > >> >> > > > > > > > - *Next-generation system for monitoring and code >> > > >> >> tracing: >> > > >> >> > > > design >> > > >> >> > > > > > and >> > > >> >> > > > > > > > usage, exporters configuration (JMX, SQL, >> > > OpenCensus) >> > > >> * >> > > >> >> > > > > > > > - *Ignite Machine Learning major upgrade: a >> > revised >> > > >> >> approach >> > > >> >> > > for >> > > >> >> > > > > > > models >> > > >> >> > > > > > > > training/evaluation, models importing from Spark >> > ML, >> > > >> >> XGBoost >> > > >> >> > > and >> > > >> >> > > > > > much >> > > >> >> > > > > > > > more >> > > >> >> > > > > > > > * >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > >> > > >> >> > > > > > > > - >> > > >> >> > > > > > > > Denis >> > > >> >> > > > > > > > >> > > >> >> > > > > > > >> > > >> >> > > > > > >> > > >> >> > > > > >> > > >> >> > > > >> > > >> >> > > >> > > >> >> > >> > > >> >> >> > > >> > >> > > >> >> > > > >> > > >> >
