Re: Ignite 2.8 announcement plan

That was published as a public page and I can see it in the feed of the latest ASF blog posts: https://blogs.apache.org/ Could also open from my mobile over a cellular network. - Denis On Wed, Mar 11, 2020 at 3:23 PM Maxim Muzafarov wrote: > Denis, Folks, > > It the

Re: Ignite 2.8 announcement plan

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 wrote: > > Folks, > > I've published the blog post: > https://blogs.apache.org/ign

Re: Ignite 2.8 announcement plan

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

Re: Ignite 2.8 announcement plan

>> 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 r

Re: Ignite 2.8 announcement plan

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 wrote: > Denis, > > >> the b

Re: Ignite 2.8 announcement plan

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 wrote: > Pavel, thank you. I referred to your article from a blog post to be > published on blogs.apache.org. Please feel free

Re: Ignite 2.8 announcement plan

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=shari

Re: Ignite 2.8 announcement plan

Published: https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.8/ On Sat, Mar 7, 2020 at 1:49 AM Pavel Tupitsyn 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 wrote: > >> Pavel

Re: Ignite 2.8 announcement plan

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 wrote: > Pavel, > > Thanks for clarifying the way partition-awareness handles topology changes. > > Please publish your article as soon as you're ready.

Re: Ignite 2.8 announcement plan

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 wrote: > Denis, thanks for the feedba

Re: Ignite 2.8 announcement plan

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

Re: Ignite 2.8 announcement plan

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 th

Re: Ignite 2.8 announcement plan

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 wrote: > Hi Pavel, > > Excellent

Re: Ignite 2.8 announcement plan

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 , how about

Re: Ignite 2.8 announcement plan

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 th

Re: Ignite 2.8 announcement plan

Sounds ineresting, will help with the post, please share the template, not sure about webinar вт, 3 мар. 2020 г., 20:59 Denis Magda : > 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. > >

Ignite 2.8 announcement plan

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 documentat