Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Ivan, I did something wrong? What should I do to release all effectively? On Thu, 5 Mar 2020 at 08:23, Denis Magda wrote: > > Ivan, > > The release of binaries is one of the final steps. There are still several > steps left before we can consider all the 2.8 release activities completed: > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.3.4.Releasedocumentaiononreadme.io > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.4.Announcerelease > > - > Denis > > > On Wed, Mar 4, 2020 at 7:57 PM Ivan Pavlukhin wrote: > > > Denis, folks, > > > > As it was already mentioned 2.8 is already in maven [1]. Consequently > > "effectively" released. In my opinion it is not correct to consider > > release in progress. > > > > Agree that 2.8.1 sounds as a proper option here. > > > > [1] https://mvnrepository.com/artifact/org.apache.ignite/ignite-core/2.8.0 > > > > Best regards, > > Ivan Pavlukhin > > > > ср, 4 мар. 2020 г. в 17:08, Denis Magda : > > > > > > Dmitriy, > > > > > > Ignite 2.8 will be announced as soon as the documentation is prepared and > > > released. Until then, the release is still considered under progress. > > Here > > > is a dedicated discussion for documentation activities. We should be > > ready > > > soon: > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-documentation-td46008.html > > > > > > Also, I've started a discussion related to our announcement steps. Please > > > check it out and get involved: > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-announcement-plan-td46238.html > > > > > > - > > > Denis > > > > > > > > > On Wed, Mar 4, 2020 at 6:29 AM Dmitriy Pavlov > > wrote: > > > > > > > Hi Folks, > > > > > > > > Unfortunately https://dist.apache.org/repos/dist/release/ignite/2.8.0/ > > is > > > > already there, so release was happened. I'm not sure it is a good idea > > to > > > > substitute binaries later. Was it announced to announce@ ? > > > > > > > > IMO, 2.8.1 is ok for that case. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > ср, 4 мар. 2020 г. в 11:29, Nikolay Izhikov : > > > > > > > > > Pavel, ++1. > > > > > > > > > > > 4 марта 2020 г., в 11:20, Pavel Tupitsyn > > > > > написал(а): > > > > > > > > > > > > Igniters, > > > > > > > > > > > > The release has already happened. > > > > > > It is on our website [1], it is on Maven [2]. > > > > > > People are using it, so I don't think we can do anything at this > > point. > > > > > > > > > > > > Bugs happen, we can't delay the release forever because of them. > > Let's > > > > > fix > > > > > > things in 2.8.1. > > > > > > > > > > > > [1] https://ignite.apache.org/download.cgi > > > > > > [2] https://mvnrepository.com/artifact/org.apache.ignite > > > > > > > > > > > > > > > > > > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov < > > nizhi...@apache.org> > > > > > wrote: > > > > > > > > > > > >> Hello, Igniters. > > > > > >> > > > > > >> Do we have a person who can fix this issue in the nearest time? > > > > > >> Right now IGNITE-12746 is Open and Unassigned. > > > > > >> > > > > > >>> 3 марта 2020 г., в 23:54, Denis Magda > > > > написал(а): > > > > > >>> > > > > > >>> Ilya, > > > > > >>> > > > > > >>> Thanks for catching that and sharing. I wonder if there are any > > other > > > > > >>> blockers that were pushed to 2.8.x version. If there are a few > > then > > > > we > > > > > >> can > > > > > >>> produce 2.8.1 shortly, otherwise, it sounds reasonable to me to > > fix > > > > the > > > > > >>> issue with putAll, update the binaries and finish the process. > > > > > >>> > > > > > >>> - > > > > > >>> Denis > > > > > >>> > > > > > >>> > > > > > >>> On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev < > > > > > >> ilya.kasnach...@gmail.com> > > > > > >>> wrote: > > > > > >>> > > > > > Hello! > > > > > > > > > > I have filed an issue > > > > > >> https://issues.apache.org/jira/browse/IGNITE-12746 > > > > > > > > > > I think this is potentially a game breaker and makes me > > recommend > > > > > >> avoiding > > > > > 2.8, if we release it without fix (for now). > > > > > > > > > > If you are using any partitioned caches, anyway. > > > > > > > > > > So I suggest we withhold 2.8. > > > > > > > > > > Regards, > > > > > -- > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov > >: > > > > > > > > > > > Ilya, > > > > > > > > > > > > I do not want to force the release no matter what happens, but > > I > > > > > think > > > > > > we should release what we have to get feedback not just from > > the > > > > > > developer community but from our users too. > > > > > > > > > > > > And fix all these issues in 2.8.1. > > > > > > > > > > > > On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev < > > > > > >> ilya.kasnach...@gmail.com> > > > > > >
Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Ivan, The release of binaries is one of the final steps. There are still several steps left before we can consider all the 2.8 release activities completed: https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.3.4.Releasedocumentaiononreadme.io https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.4.Announcerelease - Denis On Wed, Mar 4, 2020 at 7:57 PM Ivan Pavlukhin wrote: > Denis, folks, > > As it was already mentioned 2.8 is already in maven [1]. Consequently > "effectively" released. In my opinion it is not correct to consider > release in progress. > > Agree that 2.8.1 sounds as a proper option here. > > [1] https://mvnrepository.com/artifact/org.apache.ignite/ignite-core/2.8.0 > > Best regards, > Ivan Pavlukhin > > ср, 4 мар. 2020 г. в 17:08, Denis Magda : > > > > Dmitriy, > > > > Ignite 2.8 will be announced as soon as the documentation is prepared and > > released. Until then, the release is still considered under progress. > Here > > is a dedicated discussion for documentation activities. We should be > ready > > soon: > > > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-documentation-td46008.html > > > > Also, I've started a discussion related to our announcement steps. Please > > check it out and get involved: > > > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-announcement-plan-td46238.html > > > > - > > Denis > > > > > > On Wed, Mar 4, 2020 at 6:29 AM Dmitriy Pavlov > wrote: > > > > > Hi Folks, > > > > > > Unfortunately https://dist.apache.org/repos/dist/release/ignite/2.8.0/ > is > > > already there, so release was happened. I'm not sure it is a good idea > to > > > substitute binaries later. Was it announced to announce@ ? > > > > > > IMO, 2.8.1 is ok for that case. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > ср, 4 мар. 2020 г. в 11:29, Nikolay Izhikov : > > > > > > > Pavel, ++1. > > > > > > > > > 4 марта 2020 г., в 11:20, Pavel Tupitsyn > > > > написал(а): > > > > > > > > > > Igniters, > > > > > > > > > > The release has already happened. > > > > > It is on our website [1], it is on Maven [2]. > > > > > People are using it, so I don't think we can do anything at this > point. > > > > > > > > > > Bugs happen, we can't delay the release forever because of them. > Let's > > > > fix > > > > > things in 2.8.1. > > > > > > > > > > [1] https://ignite.apache.org/download.cgi > > > > > [2] https://mvnrepository.com/artifact/org.apache.ignite > > > > > > > > > > > > > > > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov < > nizhi...@apache.org> > > > > wrote: > > > > > > > > > >> Hello, Igniters. > > > > >> > > > > >> Do we have a person who can fix this issue in the nearest time? > > > > >> Right now IGNITE-12746 is Open and Unassigned. > > > > >> > > > > >>> 3 марта 2020 г., в 23:54, Denis Magda > > > написал(а): > > > > >>> > > > > >>> Ilya, > > > > >>> > > > > >>> Thanks for catching that and sharing. I wonder if there are any > other > > > > >>> blockers that were pushed to 2.8.x version. If there are a few > then > > > we > > > > >> can > > > > >>> produce 2.8.1 shortly, otherwise, it sounds reasonable to me to > fix > > > the > > > > >>> issue with putAll, update the binaries and finish the process. > > > > >>> > > > > >>> - > > > > >>> Denis > > > > >>> > > > > >>> > > > > >>> On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev < > > > > >> ilya.kasnach...@gmail.com> > > > > >>> wrote: > > > > >>> > > > > Hello! > > > > > > > > I have filed an issue > > > > >> https://issues.apache.org/jira/browse/IGNITE-12746 > > > > > > > > I think this is potentially a game breaker and makes me > recommend > > > > >> avoiding > > > > 2.8, if we release it without fix (for now). > > > > > > > > If you are using any partitioned caches, anyway. > > > > > > > > So I suggest we withhold 2.8. > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > > > > > > > > вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov >: > > > > > > > > > Ilya, > > > > > > > > > > I do not want to force the release no matter what happens, but > I > > > > think > > > > > we should release what we have to get feedback not just from > the > > > > > developer community but from our users too. > > > > > > > > > > And fix all these issues in 2.8.1. > > > > > > > > > > On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev < > > > > >> ilya.kasnach...@gmail.com> > > > > > wrote: > > > > >> > > > > >> Hello! > > > > >> > > > > >> Can we please hold back publishing AI-2.8.0-rc1 as public > Apache > > > > >> Ignite > > > > > 2.8 > > > > >> release? > > > > >> > > > > >> I have just been notified that > > > > >> > > > > > > > > > > > > > >> > > > > > > > >
Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Denis, folks, As it was already mentioned 2.8 is already in maven [1]. Consequently "effectively" released. In my opinion it is not correct to consider release in progress. Agree that 2.8.1 sounds as a proper option here. [1] https://mvnrepository.com/artifact/org.apache.ignite/ignite-core/2.8.0 Best regards, Ivan Pavlukhin ср, 4 мар. 2020 г. в 17:08, Denis Magda : > > Dmitriy, > > Ignite 2.8 will be announced as soon as the documentation is prepared and > released. Until then, the release is still considered under progress. Here > is a dedicated discussion for documentation activities. We should be ready > soon: > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-documentation-td46008.html > > Also, I've started a discussion related to our announcement steps. Please > check it out and get involved: > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-announcement-plan-td46238.html > > - > Denis > > > On Wed, Mar 4, 2020 at 6:29 AM Dmitriy Pavlov wrote: > > > Hi Folks, > > > > Unfortunately https://dist.apache.org/repos/dist/release/ignite/2.8.0/ is > > already there, so release was happened. I'm not sure it is a good idea to > > substitute binaries later. Was it announced to announce@ ? > > > > IMO, 2.8.1 is ok for that case. > > > > Sincerely, > > Dmitriy Pavlov > > > > ср, 4 мар. 2020 г. в 11:29, Nikolay Izhikov : > > > > > Pavel, ++1. > > > > > > > 4 марта 2020 г., в 11:20, Pavel Tupitsyn > > > написал(а): > > > > > > > > Igniters, > > > > > > > > The release has already happened. > > > > It is on our website [1], it is on Maven [2]. > > > > People are using it, so I don't think we can do anything at this point. > > > > > > > > Bugs happen, we can't delay the release forever because of them. Let's > > > fix > > > > things in 2.8.1. > > > > > > > > [1] https://ignite.apache.org/download.cgi > > > > [2] https://mvnrepository.com/artifact/org.apache.ignite > > > > > > > > > > > > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov > > > wrote: > > > > > > > >> Hello, Igniters. > > > >> > > > >> Do we have a person who can fix this issue in the nearest time? > > > >> Right now IGNITE-12746 is Open and Unassigned. > > > >> > > > >>> 3 марта 2020 г., в 23:54, Denis Magda > > написал(а): > > > >>> > > > >>> Ilya, > > > >>> > > > >>> Thanks for catching that and sharing. I wonder if there are any other > > > >>> blockers that were pushed to 2.8.x version. If there are a few then > > we > > > >> can > > > >>> produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix > > the > > > >>> issue with putAll, update the binaries and finish the process. > > > >>> > > > >>> - > > > >>> Denis > > > >>> > > > >>> > > > >>> On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev < > > > >> ilya.kasnach...@gmail.com> > > > >>> wrote: > > > >>> > > > Hello! > > > > > > I have filed an issue > > > >> https://issues.apache.org/jira/browse/IGNITE-12746 > > > > > > I think this is potentially a game breaker and makes me recommend > > > >> avoiding > > > 2.8, if we release it without fix (for now). > > > > > > If you are using any partitioned caches, anyway. > > > > > > So I suggest we withhold 2.8. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov : > > > > > > > Ilya, > > > > > > > > I do not want to force the release no matter what happens, but I > > > think > > > > we should release what we have to get feedback not just from the > > > > developer community but from our users too. > > > > > > > > And fix all these issues in 2.8.1. > > > > > > > > On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev < > > > >> ilya.kasnach...@gmail.com> > > > > wrote: > > > >> > > > >> Hello! > > > >> > > > >> Can we please hold back publishing AI-2.8.0-rc1 as public Apache > > > >> Ignite > > > > 2.8 > > > >> release? > > > >> > > > >> I have just been notified that > > > >> > > > > > > > > > > >> > > > > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated > > > >> > > > > > > > > > > >> > > > > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed > > > >> are flaky: they seem to deadlock on putAll sorted keys maps. They > > > used > > > to > > > >> pass solidly on 2.7, but fail on master and ignite-2.8. > > > >> > > > >> (They fail around 1 time out of 10, so just run them 25 times to > > > >> check) > > > >> > > > >> If there is indeed a deadlock, this would become a blocker to this > > > > release, > > > >> in my opinion, but I need some time to check. > > > >> > > > >> Regards, > > > >> -- > > > >> Ilya Kasnacheev > > > >> > > > >> > > > >> вс, 1 мар. 2020 г. в 11:29,
Re: Ignite 2.8 documentation
> That's right, only C++ and .NET clients have partition awareness Are your sure? Was not the feature implemented for java thin client in [1]? [1] https://issues.apache.org/jira/browse/IGNITE-11898 Best regards, Ivan Pavlukhin ср, 4 мар. 2020 г. в 18:18, Denis Magda : > > Maxim, > > Yes, it's preferable to have metrics pages fully completed even though the > feature is an experimental state. We want to encourage to try it out and > switch to the new APIs eventually. Without technical instructions available > our users will have a hard time checking the new capabilities. > > Nikolay, thanks a lot! > > - > Denis > > > On Wed, Mar 4, 2020 at 8:52 AM Nikolay Izhikov wrote: > > > I think yes. > > > > I will prepare documentation shortly. > > > > > 4 марта 2020 г., в 17:50, Maxim Muzafarov > > написал(а): > > > > > > Folks, > > > > > > > > > Do we need a fully complete public documentation for metrics marked > > > with @ExperimentalFeature? The API can significantly be changed. > > > > > > On Wed, 4 Mar 2020 at 17:10, Artem Budnikov > > wrote: > > >> > > >> The only feature that is left is "WAL page compression" > > >> > > >> The three other features are limitations that were present in Ignite > > >> 2.7 and now they are removed. Since they were never mentioned in the > > >> docs, there is nothing to do. > > >> > > >> -Artem > > >> > > >> On 04.03.2020 17:02, Denis Magda wrote: > > I'll work on the following items today and tomorrow: > > > > - JDBC: Support for query cancellation > > > > > > - JDBC: Support for query timeout > > > > > > - suspend/resume for pessimistic transactions > > > > > > - WAL page compression > > > > > > >>> Artem, are these the only tickets left apart from the metrics & > > >>> monitoring? @Nikolay > > >>> Izhikov how soon will you be able to finish the > > >>> metrics documentation pages? > > >>> > > >>> - > > >>> Denis > > >>> > > >>> > > >>> On Wed, Mar 4, 2020 at 2:55 AM Artem Budnikov > > >>> wrote: > > >>> > > Hi everyone, > > > > I have created the docs for the following items so far: > > > > -Default Ignite work dir location > > > > > > https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory > > > > - Baseline auto-adjust feature > > > > > > https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment > > > > - Cluster (de)activation events documentation > > > > > > https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events > > > > - Remove SqlQuery documentation > > done > > > > - Partition awareness for thin clients > > > > > > https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness > > > > > > https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness > > > > - Transactions support in java thin client > > > > > > https://apacheignite.readme.io/docs/key-value-28#section-client-transactions > > > > - KILL QUERY command > > > > > > https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query > > > > - Move rebalance configuration properties to the > > IgniteConfiguration level > > > > > > https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration > > > > - Renamed IGNITE schema to SYS > > done > > > > I'll work on the following items today and tomorrow: > > > > - JDBC: Support for query cancellation > > - JDBC: Support for query timeout > > - suspend/resume for pessimistic transactions > > - WAL page compression > > > > > > Nikolay, > > > > How is your progress with the Metrics and System Views documentation? > > > > > > Artem Budnikov > > Technical Writergridgain.com > > > > On 03.03.2020 19:06, Maxim Muzafarov wrote: > > > > Folks, > > > > This is in the `Ignite Core` section, so I think mostly related to > > java functionality and thin client protocol extension [1]. Sorry for > > not being too accurate with this statement > > . > > The same change is mentioned for C++ and .NET sections of the release > > notes (but not for other thin clients). > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11898 > > > > On Tue, 3 Mar 2020 at 17:33, Igor Sapego < > > isap...@apache.org> wrote: > > > > That's right, only C++ and .NET clients have partition awareness > > > > Best Regards, > > Igor > > > > > > On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov > > > > wrote: > > >
Re: Out of memory with eviction failure on persisted cache
Hi Evgenii, I am individually Put()ing the elements using PutIfAbsent(). Each element can range 2kb-35Kb in size. Actually, the process that writes the data does not write the data directly to the cache, it uses a compute function to send the payload to the process that is doing the reading. The compute function applies validation logic and uses PutIfAbsent() to write the data into the cache. Sorry for the confusion. Raymond. On Thu, Mar 5, 2020 at 1:09 PM Evgenii Zhuravlev wrote: > Hi, > > How are you loading the data? Do you use putAll or DataStreamer? > > Evgenii > > ср, 4 мар. 2020 г. в 15:37, Raymond Wilson : > >> To add some further detail: >> >> There are two processes interacting with the cache. One process is writing >> data into the cache, while the second process is extracting data from the >> cache using a continuous query. The process that is the reader of the data >> is throwing the exception. >> >> Increasing the cache size further to 256 Mb resolves the problem for this >> data set, however we have data sets more than 100 times this size which we >> will be processing. >> >> Thanks, >> Raymond. >> >> >> On Thu, Mar 5, 2020 at 12:10 PM Raymond Wilson < >> raymond_wil...@trimble.com> >> wrote: >> >> > I've been having a sporadic issue with the Ignite 2.7.5 JVM halting due >> to >> > out of memory error related to a cache with persistence enabled >> > >> > I just upgraded to the C#.Net, Ignite 2.7.6 client to pick up support >> for >> > C# affinity functions and now have this issue appearing regularly while >> > adding around 400Mb of data into the cache which is configured to have >> > 128Mb of memory (this was 64Mb but I increased it to see if the failure >> > would resolve. >> > >> > The error I get is: >> > >> > 2020-03-05 11:58:57,568 [542] ERR [MutableCacheComputeServer] JVM will >> be >> > halted immediately due to the failure: [failureCtx=FailureContext >> > [type=CRITICAL_ERROR, err=class o.a.i.i.mem.IgniteOutOfMemoryException: >> > Failed to find a page for eviction [segmentCapacity=1700, loaded=676, >> > maxDirtyPages=507, dirtyPages=675, cpPages=0, pinnedInSegment=2, >> > failedToPrepare=675] >> > Out of memory in data region [name=TAGFileBufferQueue, initSize=128.0 >> MiB, >> > maxSize=128.0 MiB, persistenceEnabled=true] Try the following: >> > ^-- Increase maximum off-heap memory size >> > (DataRegionConfiguration.maxSize) >> > ^-- Enable Ignite persistence >> > (DataRegionConfiguration.persistenceEnabled) >> > ^-- Enable eviction or expiration policies]] >> > >> > I'm not running an eviction policy as I thought this was not required >> for >> > caches with persistence enabled. >> > >> > I'm surprised by this behaviour as I expected the persistence mechanism >> to >> > handle it. The error relating to failure to find a page for eviction >> > suggest the persistence mechanism has fallen behind. If this is the >> case, >> > this seems like an unfriendly failure mode. >> > >> > Thanks, >> > Raymond. >> > >> > >> > >> >
Re: Out of memory with eviction failure on persisted cache
Hi, How are you loading the data? Do you use putAll or DataStreamer? Evgenii ср, 4 мар. 2020 г. в 15:37, Raymond Wilson : > To add some further detail: > > There are two processes interacting with the cache. One process is writing > data into the cache, while the second process is extracting data from the > cache using a continuous query. The process that is the reader of the data > is throwing the exception. > > Increasing the cache size further to 256 Mb resolves the problem for this > data set, however we have data sets more than 100 times this size which we > will be processing. > > Thanks, > Raymond. > > > On Thu, Mar 5, 2020 at 12:10 PM Raymond Wilson > > wrote: > > > I've been having a sporadic issue with the Ignite 2.7.5 JVM halting due > to > > out of memory error related to a cache with persistence enabled > > > > I just upgraded to the C#.Net, Ignite 2.7.6 client to pick up support for > > C# affinity functions and now have this issue appearing regularly while > > adding around 400Mb of data into the cache which is configured to have > > 128Mb of memory (this was 64Mb but I increased it to see if the failure > > would resolve. > > > > The error I get is: > > > > 2020-03-05 11:58:57,568 [542] ERR [MutableCacheComputeServer] JVM will be > > halted immediately due to the failure: [failureCtx=FailureContext > > [type=CRITICAL_ERROR, err=class o.a.i.i.mem.IgniteOutOfMemoryException: > > Failed to find a page for eviction [segmentCapacity=1700, loaded=676, > > maxDirtyPages=507, dirtyPages=675, cpPages=0, pinnedInSegment=2, > > failedToPrepare=675] > > Out of memory in data region [name=TAGFileBufferQueue, initSize=128.0 > MiB, > > maxSize=128.0 MiB, persistenceEnabled=true] Try the following: > > ^-- Increase maximum off-heap memory size > > (DataRegionConfiguration.maxSize) > > ^-- Enable Ignite persistence > > (DataRegionConfiguration.persistenceEnabled) > > ^-- Enable eviction or expiration policies]] > > > > I'm not running an eviction policy as I thought this was not required for > > caches with persistence enabled. > > > > I'm surprised by this behaviour as I expected the persistence mechanism > to > > handle it. The error relating to failure to find a page for eviction > > suggest the persistence mechanism has fallen behind. If this is the case, > > this seems like an unfriendly failure mode. > > > > Thanks, > > Raymond. > > > > > > >
Re: Out of memory with eviction failure on persisted cache
To add some further detail: There are two processes interacting with the cache. One process is writing data into the cache, while the second process is extracting data from the cache using a continuous query. The process that is the reader of the data is throwing the exception. Increasing the cache size further to 256 Mb resolves the problem for this data set, however we have data sets more than 100 times this size which we will be processing. Thanks, Raymond. On Thu, Mar 5, 2020 at 12:10 PM Raymond Wilson wrote: > I've been having a sporadic issue with the Ignite 2.7.5 JVM halting due to > out of memory error related to a cache with persistence enabled > > I just upgraded to the C#.Net, Ignite 2.7.6 client to pick up support for > C# affinity functions and now have this issue appearing regularly while > adding around 400Mb of data into the cache which is configured to have > 128Mb of memory (this was 64Mb but I increased it to see if the failure > would resolve. > > The error I get is: > > 2020-03-05 11:58:57,568 [542] ERR [MutableCacheComputeServer] JVM will be > halted immediately due to the failure: [failureCtx=FailureContext > [type=CRITICAL_ERROR, err=class o.a.i.i.mem.IgniteOutOfMemoryException: > Failed to find a page for eviction [segmentCapacity=1700, loaded=676, > maxDirtyPages=507, dirtyPages=675, cpPages=0, pinnedInSegment=2, > failedToPrepare=675] > Out of memory in data region [name=TAGFileBufferQueue, initSize=128.0 MiB, > maxSize=128.0 MiB, persistenceEnabled=true] Try the following: > ^-- Increase maximum off-heap memory size > (DataRegionConfiguration.maxSize) > ^-- Enable Ignite persistence > (DataRegionConfiguration.persistenceEnabled) > ^-- Enable eviction or expiration policies]] > > I'm not running an eviction policy as I thought this was not required for > caches with persistence enabled. > > I'm surprised by this behaviour as I expected the persistence mechanism to > handle it. The error relating to failure to find a page for eviction > suggest the persistence mechanism has fallen behind. If this is the case, > this seems like an unfriendly failure mode. > > Thanks, > Raymond. > > >
Out of memory with eviction failure on persisted cache
I've been having a sporadic issue with the Ignite 2.7.5 JVM halting due to out of memory error related to a cache with persistence enabled I just upgraded to the C#.Net, Ignite 2.7.6 client to pick up support for C# affinity functions and now have this issue appearing regularly while adding around 400Mb of data into the cache which is configured to have 128Mb of memory (this was 64Mb but I increased it to see if the failure would resolve. The error I get is: 2020-03-05 11:58:57,568 [542] ERR [MutableCacheComputeServer] JVM will be halted immediately due to the failure: [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class o.a.i.i.mem.IgniteOutOfMemoryException: Failed to find a page for eviction [segmentCapacity=1700, loaded=676, maxDirtyPages=507, dirtyPages=675, cpPages=0, pinnedInSegment=2, failedToPrepare=675] Out of memory in data region [name=TAGFileBufferQueue, initSize=128.0 MiB, maxSize=128.0 MiB, persistenceEnabled=true] Try the following: ^-- Increase maximum off-heap memory size (DataRegionConfiguration.maxSize) ^-- Enable Ignite persistence (DataRegionConfiguration.persistenceEnabled) ^-- Enable eviction or expiration policies]] I'm not running an eviction policy as I thought this was not required for caches with persistence enabled. I'm surprised by this behaviour as I expected the persistence mechanism to handle it. The error relating to failure to find a page for eviction suggest the persistence mechanism has fallen behind. If this is the case, this seems like an unfriendly failure mode. Thanks, Raymond.
Distributed DMX Lighting Control With Apache Ignite.NET
Hi Igniters, Let me introduce you to Mike James, who has been working on a gripping project that uses Apache Ignite as a backbone for a distributed DMX Control system. That's a use case of the entertainment industry and, hopefully, many rockstars will switch to the solution to produce light effects and shows during their performances ;) Check this two-part series by Mike: - Intro and use case: https://lightconsole.dev/2020/02/26/intro-to-dmx-control-systems/ - Architecture: https://lightconsole.dev/2020/03/04/distributing-dmx-compute-with-apache-ignite/ You might be interested to see how the system relies on various capabilities of Ignite to make the things working at scale - compute, storage, service grid, etc. @Pavel Tupitsyn, I would especially want to connect you with Mike, who can share his feedback in regards to our .NET component. Mike, stay in touch with Pavel, who is our main maintainer and contributor to .NET. - Denis
[jira] [Created] (IGNITE-12749) Unsupported operation exception on node stop if collisionspi not null
Nikolay Izhikov created IGNITE-12749:
Summary: Unsupported operation exception on node stop if
collisionspi not null
Key: IGNITE-12749
URL: https://issues.apache.org/jira/browse/IGNITE-12749
Project: Ignite
Issue Type: Bug
Reporter: Nikolay Izhikov
If collision spi specified then on the node stop there are exception:
{noformat}
java.lang.UnsupportedOperationException
at
org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1542)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:376)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2697)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2569)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2660)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2623)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:339)
at org.apache.ignite.Ignition.stop(Ignition.java:223)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1316)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1361)
{noformat}
The issue in the next line:
{code:java}
public GridJobProcessor(GridKernalContext ctx) {
// Collision manager is already started and is fully functional.
jobAlwaysActivate = !ctx.collision().enabled();
activeJobs = jobAlwaysActivate ? new ConcurrentHashMap() :
new JobsMap(1024, 0.75f, 256);
{code}
We need replace JobsMap with the correct implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Apache Ignite ML & Python
Andrei,
I am also working with Apache Ignite ML and am interested in providing
wrappers for Ignite ML API, but am wondering if instead of simply recreating
the low level Java API for ML inside Python, how about creating some higher
level services "Auto ML" workflow ? For example:
1. here is raw dataset, already inside this cluster cache "myName", with
Label column "MyLable" , take N samples tell me which appear to be numeric,
unique id, and categorical values?
2. based on N samples, , please run some analysis and tell me the top 5
feature columns in terms of predictive value using algorithm = RandonForest
3. do a batch run, sample size = N, using these preprocessing steps list
{impute, scale, etc} and algorithms (knn, Decision Tree, etc} and give me a
report of accuracies obtain with each.
In other words, we have a simple sample in the Tutorial demo where these
all run and then we compare outputs - why not automate these with a Python
Notebook UI of some sort?
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Apache Ignite ML & Python
Dear Community, I was very inspired in Ignite ML and I wanted to try it with Python. Particularly I was interested in compares Ignite ML VS Spark ML However, I came across the fact that pyignite component allows only to perform basic cache operations through the API and it has nothing to do with Ignite ML. I have discussed this issue with Alexey Zinoviev and he suggested to describe here all required features which are not presented now in Ignite. Therefore the list of required features: * Ignite ML and pyignite integration. Ignite ML is a fairly versatile ML, just inside driving on Ignite primitives, so Ignite ML and pyignite compatibility requires a lot of java code using py4j library to wrap Ignite ML with python. Also, I'm sure lots of python developers will be appreciated opportunity to test this solution in their tasks. * Ignite ML and PySpark integration. The really interesting case is using pyignite ML with data preprocessed via pyspark. As soon as I know the current version of Ignite supports only integration with Spark (not Pyspark) I hope I wrote this letter in accordance with the rules of the community. Also, I hope these cases will be interested in the dev community. BG Andrei Gavrilov. Software Engineer. EPAM Systems -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Reference of local service.
Vyacheslav, Denis, hi again. >>> I agree with the proposal to introduce a new method which returns proxy include the case of locally deployed services. I see one is restricted to use an interface for service with IgniteServiceProcessor#serviceProxy(…): A.ensure(svcItf.isInterface(), "Service class must be an interface: " + svcItf); What if we change IgniteService#serviceProxy(...) so that it will return proxy everytime? That looks safe for user code. Doing so we might only deprecate IgniteService#service(...). вт, 3 мар. 2020 г., 11:03 Vyacheslav Daradur : > Denis, finally I understood your arguments about interfaces check, thank > you for the explanation. > > I agree with the proposal to introduce a new method which returns proxy > include the case of locally deployed services. > > Also, such a method should be able to work in mode "local services > preferred", perhaps with load-balancing (in case of multiple locally > deployed instances). This allows our end-users to reach better performance. > > > > On Mon, Mar 2, 2020 at 7:51 PM Denis Mekhanikov > wrote: > > > Vyacheslav, > > > > You can't make service interfaces extend > > *org.apache.ignite.services.Service*. Currently it works perfectly if > > *org.apache.ignite.services.Service* and a user-defined interface are > > independent. This is actually the case in our current examples: > > > > > https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/servicegrid/SimpleMapService.java > > I mentioned the *Serializable* interface just as an example of an > interface > > that can be present, but it's not the one that is going to be called by a > > user. > > > > What I'm trying to say is that there is no way to say whether the service > > is going to be used through a proxy only, or usage of a local instance is > > also possible. > > > > Vladimir, > > > > I don't like the idea, that enabling or disabling of metrics will change > > the behaviour of the component you collect the metrics for. Such > behaviour > > is far from obvious. > > > > Nikolay, > > > > I agree, that such approach is valid and makes total sense. But making > the > > *IgniteServices#serviceProxy()* method always return a proxy instead of a > > local instance will change the public contract. The javadoc currently > says > > the following: > > > > > If service is available locally, then local instance is returned, > > > otherwise, a remote proxy is dynamically created and provided for the > > > specified service. > > > > > > I propose introducing a new method that will always return a service > proxy > > regardless of local availability, and deprecating *serviceProxy()* and > > *service() > > *methods. What do you think? > > > > Denis > > > > пн, 2 мар. 2020 г. в 16:08, Nikolay Izhikov : > > > > > Hello, Vladimir. > > > > > > > What if we just provide an option to disable service metrics at all? > > > > > > I don't think we should create an explicit property for service > metrics. > > > We will implement the way to disable any metrics in the scope of > > > IGNITE-11927 [1]. > > > > > > > Usage of a proxy instead of service instances can lead to performance > > > > degradation for local instances, which is another argument against > such > > > change. > > > > > > As far as I know, many and many modern frameworks use a proxy approach. > > > Just to name one - Spring framework works with the proxy. > > > > > > We should measure the impact on the performance that brings > proxy+metric > > > and after it make the decision on local service metrics implementation. > > > Vladimir, can you, as a contributor of this task make this measurement? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11927 > > > > > > пн, 2 мар. 2020 г. в 12:56, Vladimir Steshin : > > > > > > > Denis, Vyacheslav, hi. > > > > > > > > What if we just provide an option to disable service metrics at all? > It > > > > would keep direct references for local services. Also, we can make > > > service > > > > metrics disabled by default to keep current code working. A warning > of > > > > local service issues will be set with the option. > > > > > > > > пн, 2 мар. 2020 г. в 11:26, Vyacheslav Daradur >: > > > > > > > > > >> Moreover, I don't see a way of implementing such a check. Are > you > > > > going > > > > > to look just for any interface? What about Serializable? Will it > do? > > > > > > > > > > The check should look for the interface which implements > > > > > "org.apache.ignite.services.Service", it covers the requirement to > be > > > > > Serializable. > > > > > > > > > > >> For now though the best thing we can do is to calculate remote > > > > > invocations only, since all of them go through a proxy. > > > > > > > > > > Let's introduce a system property to manage local services > > monitoring: > > > > > - local services monitoring will be disabled by default - to avoid > > any > > > > > backward compatibility issues; > > > > > - local services monitoring can
Re: Ignite 2.8 documentation
Maxim, Yes, it's preferable to have metrics pages fully completed even though the feature is an experimental state. We want to encourage to try it out and switch to the new APIs eventually. Without technical instructions available our users will have a hard time checking the new capabilities. Nikolay, thanks a lot! - Denis On Wed, Mar 4, 2020 at 8:52 AM Nikolay Izhikov wrote: > I think yes. > > I will prepare documentation shortly. > > > 4 марта 2020 г., в 17:50, Maxim Muzafarov > написал(а): > > > > Folks, > > > > > > Do we need a fully complete public documentation for metrics marked > > with @ExperimentalFeature? The API can significantly be changed. > > > > On Wed, 4 Mar 2020 at 17:10, Artem Budnikov > wrote: > >> > >> The only feature that is left is "WAL page compression" > >> > >> The three other features are limitations that were present in Ignite > >> 2.7 and now they are removed. Since they were never mentioned in the > >> docs, there is nothing to do. > >> > >> -Artem > >> > >> On 04.03.2020 17:02, Denis Magda wrote: > I'll work on the following items today and tomorrow: > > - JDBC: Support for query cancellation > > > - JDBC: Support for query timeout > > > - suspend/resume for pessimistic transactions > > > - WAL page compression > > > >>> Artem, are these the only tickets left apart from the metrics & > >>> monitoring? @Nikolay > >>> Izhikov how soon will you be able to finish the > >>> metrics documentation pages? > >>> > >>> - > >>> Denis > >>> > >>> > >>> On Wed, Mar 4, 2020 at 2:55 AM Artem Budnikov > >>> wrote: > >>> > Hi everyone, > > I have created the docs for the following items so far: > > -Default Ignite work dir location > > > https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory > > - Baseline auto-adjust feature > > > https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment > > - Cluster (de)activation events documentation > > > https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events > > - Remove SqlQuery documentation > done > > - Partition awareness for thin clients > > > https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness > > > https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness > > - Transactions support in java thin client > > > https://apacheignite.readme.io/docs/key-value-28#section-client-transactions > > - KILL QUERY command > > > https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query > > - Move rebalance configuration properties to the > IgniteConfiguration level > > > https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration > > - Renamed IGNITE schema to SYS > done > > I'll work on the following items today and tomorrow: > > - JDBC: Support for query cancellation > - JDBC: Support for query timeout > - suspend/resume for pessimistic transactions > - WAL page compression > > > Nikolay, > > How is your progress with the Metrics and System Views documentation? > > > Artem Budnikov > Technical Writergridgain.com > > On 03.03.2020 19:06, Maxim Muzafarov wrote: > > Folks, > > This is in the `Ignite Core` section, so I think mostly related to > java functionality and thin client protocol extension [1]. Sorry for > not being too accurate with this statement > . > The same change is mentioned for C++ and .NET sections of the release > notes (but not for other thin clients). > > > [1] https://issues.apache.org/jira/browse/IGNITE-11898 > > On Tue, 3 Mar 2020 at 17:33, Igor Sapego < > isap...@apache.org> wrote: > > That's right, only C++ and .NET clients have partition awareness > > Best Regards, > Igor > > > On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov > > wrote: > > > Hi everyone, > > Looks like the following line from the Ignite 2.8 release notes is a > bit > of an overstatement and should be removed: > > > Added support best effort affinity for thin clients (partition > awareness) > > Java thin client does not support partition awareness. Nodejs and > python > thin clients from the distribution package do not have signs of this > feature as well. > > Igor, > > Could you please confirm or deny this? > > -Artem > > Artem Budnikov >
Re: Ignite 2.8 documentation
I think yes. I will prepare documentation shortly. > 4 марта 2020 г., в 17:50, Maxim Muzafarov написал(а): > > Folks, > > > Do we need a fully complete public documentation for metrics marked > with @ExperimentalFeature? The API can significantly be changed. > > On Wed, 4 Mar 2020 at 17:10, Artem Budnikov > wrote: >> >> The only feature that is left is "WAL page compression" >> >> The three other features are limitations that were present in Ignite >> 2.7 and now they are removed. Since they were never mentioned in the >> docs, there is nothing to do. >> >> -Artem >> >> On 04.03.2020 17:02, Denis Magda wrote: I'll work on the following items today and tomorrow: - JDBC: Support for query cancellation - JDBC: Support for query timeout - suspend/resume for pessimistic transactions - WAL page compression >>> Artem, are these the only tickets left apart from the metrics & >>> monitoring? @Nikolay >>> Izhikov how soon will you be able to finish the >>> metrics documentation pages? >>> >>> - >>> Denis >>> >>> >>> On Wed, Mar 4, 2020 at 2:55 AM Artem Budnikov >>> wrote: >>> Hi everyone, I have created the docs for the following items so far: -Default Ignite work dir location https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory - Baseline auto-adjust feature https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment - Cluster (de)activation events documentation https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events - Remove SqlQuery documentation done - Partition awareness for thin clients https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness - Transactions support in java thin client https://apacheignite.readme.io/docs/key-value-28#section-client-transactions - KILL QUERY command https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query - Move rebalance configuration properties to the IgniteConfiguration level https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration - Renamed IGNITE schema to SYS done I'll work on the following items today and tomorrow: - JDBC: Support for query cancellation - JDBC: Support for query timeout - suspend/resume for pessimistic transactions - WAL page compression Nikolay, How is your progress with the Metrics and System Views documentation? Artem Budnikov Technical Writergridgain.com On 03.03.2020 19:06, Maxim Muzafarov wrote: Folks, This is in the `Ignite Core` section, so I think mostly related to java functionality and thin client protocol extension [1]. Sorry for not being too accurate with this statement . The same change is mentioned for C++ and .NET sections of the release notes (but not for other thin clients). [1] https://issues.apache.org/jira/browse/IGNITE-11898 On Tue, 3 Mar 2020 at 17:33, Igor Sapego wrote: That's right, only C++ and .NET clients have partition awareness Best Regards, Igor On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov wrote: Hi everyone, Looks like the following line from the Ignite 2.8 release notes is a bit of an overstatement and should be removed: Added support best effort affinity for thin clients (partition awareness) Java thin client does not support partition awareness. Nodejs and python thin clients from the distribution package do not have signs of this feature as well. Igor, Could you please confirm or deny this? -Artem Artem Budnikov Technical Writergridgain.com On 03.03.2020 01:47, Denis Magda wrote: Hi Alexey, Thanks for updating the documentation. The update process is cumbersome as of now. What will happen is that we will be replacing the content of the current pages (pre 2.8 pages) with the content from the 2.8 versions. Once the text is copied manually, a 2.8 version of the page will be deleted. I would advise Artem to do that this time and update the wiki page with more details:https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document
Re: Ignite 2.8 documentation
Folks, Do we need a fully complete public documentation for metrics marked with @ExperimentalFeature? The API can significantly be changed. On Wed, 4 Mar 2020 at 17:10, Artem Budnikov wrote: > > The only feature that is left is "WAL page compression" > > The three other features are limitations that were present in Ignite > 2.7 and now they are removed. Since they were never mentioned in the > docs, there is nothing to do. > > -Artem > > On 04.03.2020 17:02, Denis Magda wrote: > >> I'll work on the following items today and tomorrow: > >> > >> - JDBC: Support for query cancellation > >> > >> > >> - JDBC: Support for query timeout > >> > >> > >> - suspend/resume for pessimistic transactions > >> > >> > >> - WAL page compression > >> > >> > > Artem, are these the only tickets left apart from the metrics & > > monitoring? @Nikolay > > Izhikov how soon will you be able to finish the > > metrics documentation pages? > > > > - > > Denis > > > > > > On Wed, Mar 4, 2020 at 2:55 AM Artem Budnikov > > wrote: > > > >> Hi everyone, > >> > >> I have created the docs for the following items so far: > >> > >> -Default Ignite work dir location > >> > >> > >> https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory > >> > >> - Baseline auto-adjust feature > >> > >> > >> https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment > >> > >> - Cluster (de)activation events documentation > >> > >> > >> https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events > >> > >> - Remove SqlQuery documentation > >> done > >> > >> - Partition awareness for thin clients > >> > >> > >> https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness > >> > >> > >> https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness > >> > >> - Transactions support in java thin client > >> > >> > >> https://apacheignite.readme.io/docs/key-value-28#section-client-transactions > >> > >> - KILL QUERY command > >> > >> https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query > >> > >> - Move rebalance configuration properties to the > >> IgniteConfiguration level > >> > >> > >> https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration > >> > >> - Renamed IGNITE schema to SYS > >> done > >> > >> I'll work on the following items today and tomorrow: > >> > >> - JDBC: Support for query cancellation > >> - JDBC: Support for query timeout > >> - suspend/resume for pessimistic transactions > >> - WAL page compression > >> > >> > >> Nikolay, > >> > >> How is your progress with the Metrics and System Views documentation? > >> > >> > >> Artem Budnikov > >> Technical Writergridgain.com > >> > >> On 03.03.2020 19:06, Maxim Muzafarov wrote: > >> > >> Folks, > >> > >> This is in the `Ignite Core` section, so I think mostly related to > >> java functionality and thin client protocol extension [1]. Sorry for > >> not being too accurate with this statement > >> . > >> The same change is mentioned for C++ and .NET sections of the release > >> notes (but not for other thin clients). > >> > >> > >> [1] https://issues.apache.org/jira/browse/IGNITE-11898 > >> > >> On Tue, 3 Mar 2020 at 17:33, Igor Sapego > >> wrote: > >> > >> That's right, only C++ and .NET clients have partition awareness > >> > >> Best Regards, > >> Igor > >> > >> > >> On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov > >> > >> wrote: > >> > >> > >> Hi everyone, > >> > >> Looks like the following line from the Ignite 2.8 release notes is a bit > >> of an overstatement and should be removed: > >> > >> > >> Added support best effort affinity for thin clients (partition awareness) > >> > >> Java thin client does not support partition awareness. Nodejs and python > >> thin clients from the distribution package do not have signs of this > >> feature as well. > >> > >> Igor, > >> > >> Could you please confirm or deny this? > >> > >> -Artem > >> > >> Artem Budnikov > >> Technical Writergridgain.com > >> > >> On 03.03.2020 01:47, Denis Magda wrote: > >> > >> Hi Alexey, > >> > >> Thanks for updating the documentation. The update process is cumbersome as > >> of now. What will happen is that we will be replacing the content of the > >> current pages (pre 2.8 pages) with the content from the 2.8 versions. Once > >> the text is copied manually, a 2.8 version of the page will be deleted. I > >> would advise Artem to do that this time and update the wiki page with more > >> details:https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document > >> > >> Also, why should we release this > >> page?https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms > >> > >> - > >> Denis > >> > >> > >> On Sun, Mar 1, 2020
[jira] [Created] (IGNITE-12748) PushMetricsExporterAdapter based exporters could lead to exceptions on getting gauge value
Andrey N. Gura created IGNITE-12748:
---
Summary: PushMetricsExporterAdapter based exporters could lead to
exceptions on getting gauge value
Key: IGNITE-12748
URL: https://issues.apache.org/jira/browse/IGNITE-12748
Project: Ignite
Issue Type: Bug
Reporter: Andrey N. Gura
Assignee: Andrey N. Gura
Fix For: 2.9
The special case of the problem is
https://issues.apache.org/jira/browse/IGNITE-12735.
The problem is {{PushMetricsExporterAdapter}} based exporter could access to
the components that are not initialized yet via gauge's supplier.
Task that reposnsible for exporting should be initialized in
{{onContextIntialized0()}} method instead of {{spiStart()}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
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 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 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 > wrote: > > > 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. > > > > > > 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 > > > , would you be able to present the ML part? > > > @Nikolay > > > Izhikov or @Andrey Gura > 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 > > > > > >
Re: Ignite 2.8 documentation
The only feature that is left is "WAL page compression" The three other features are limitations that were present in Ignite 2.7 and now they are removed. Since they were never mentioned in the docs, there is nothing to do. -Artem On 04.03.2020 17:02, Denis Magda wrote: I'll work on the following items today and tomorrow: - JDBC: Support for query cancellation - JDBC: Support for query timeout - suspend/resume for pessimistic transactions - WAL page compression Artem, are these the only tickets left apart from the metrics & monitoring? @Nikolay Izhikov how soon will you be able to finish the metrics documentation pages? - Denis On Wed, Mar 4, 2020 at 2:55 AM Artem Budnikov wrote: Hi everyone, I have created the docs for the following items so far: -Default Ignite work dir location https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory - Baseline auto-adjust feature https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment - Cluster (de)activation events documentation https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events - Remove SqlQuery documentation done - Partition awareness for thin clients https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness - Transactions support in java thin client https://apacheignite.readme.io/docs/key-value-28#section-client-transactions - KILL QUERY command https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query - Move rebalance configuration properties to the IgniteConfiguration level https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration - Renamed IGNITE schema to SYS done I'll work on the following items today and tomorrow: - JDBC: Support for query cancellation - JDBC: Support for query timeout - suspend/resume for pessimistic transactions - WAL page compression Nikolay, How is your progress with the Metrics and System Views documentation? Artem Budnikov Technical Writergridgain.com On 03.03.2020 19:06, Maxim Muzafarov wrote: Folks, This is in the `Ignite Core` section, so I think mostly related to java functionality and thin client protocol extension [1]. Sorry for not being too accurate with this statement . The same change is mentioned for C++ and .NET sections of the release notes (but not for other thin clients). [1] https://issues.apache.org/jira/browse/IGNITE-11898 On Tue, 3 Mar 2020 at 17:33, Igor Sapego wrote: That's right, only C++ and .NET clients have partition awareness Best Regards, Igor On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov wrote: Hi everyone, Looks like the following line from the Ignite 2.8 release notes is a bit of an overstatement and should be removed: Added support best effort affinity for thin clients (partition awareness) Java thin client does not support partition awareness. Nodejs and python thin clients from the distribution package do not have signs of this feature as well. Igor, Could you please confirm or deny this? -Artem Artem Budnikov Technical Writergridgain.com On 03.03.2020 01:47, Denis Magda wrote: Hi Alexey, Thanks for updating the documentation. The update process is cumbersome as of now. What will happen is that we will be replacing the content of the current pages (pre 2.8 pages) with the content from the 2.8 versions. Once the text is copied manually, a 2.8 version of the page will be deleted. I would advise Artem to do that this time and update the wiki page with more details:https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document Also, why should we release this page?https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms - Denis On Sun, Mar 1, 2020 at 7:59 AM Alexey Zinoviev wrote: Hi, Igniters, I've finished the ML documentation. I have the issue that, for example I've created a new version of page with postfix -2.8 and the page name contains this postfix. How are we going to replace the URL? Or we will replace the content from initial page? For example, I've created the new version of pagehttps://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees and moved it under new pagehttps://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees-28 How it will be processed to obtain the decision-trees url for the new page? In all case the full list of removed/replaced pages for ML is next: In the release 2.8, please remove the pages 1. https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms 2. https://dash.readme.io/project/apacheignite/v2.7.6/docs/svm-multi-class-classification 3. DeepLearning
Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Dmitriy, Ignite 2.8 will be announced as soon as the documentation is prepared and released. Until then, the release is still considered under progress. Here is a dedicated discussion for documentation activities. We should be ready soon: http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-documentation-td46008.html Also, I've started a discussion related to our announcement steps. Please check it out and get involved: http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-8-announcement-plan-td46238.html - Denis On Wed, Mar 4, 2020 at 6:29 AM Dmitriy Pavlov wrote: > Hi Folks, > > Unfortunately https://dist.apache.org/repos/dist/release/ignite/2.8.0/ is > already there, so release was happened. I'm not sure it is a good idea to > substitute binaries later. Was it announced to announce@ ? > > IMO, 2.8.1 is ok for that case. > > Sincerely, > Dmitriy Pavlov > > ср, 4 мар. 2020 г. в 11:29, Nikolay Izhikov : > > > Pavel, ++1. > > > > > 4 марта 2020 г., в 11:20, Pavel Tupitsyn > > написал(а): > > > > > > Igniters, > > > > > > The release has already happened. > > > It is on our website [1], it is on Maven [2]. > > > People are using it, so I don't think we can do anything at this point. > > > > > > Bugs happen, we can't delay the release forever because of them. Let's > > fix > > > things in 2.8.1. > > > > > > [1] https://ignite.apache.org/download.cgi > > > [2] https://mvnrepository.com/artifact/org.apache.ignite > > > > > > > > > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov > > wrote: > > > > > >> Hello, Igniters. > > >> > > >> Do we have a person who can fix this issue in the nearest time? > > >> Right now IGNITE-12746 is Open and Unassigned. > > >> > > >>> 3 марта 2020 г., в 23:54, Denis Magda > написал(а): > > >>> > > >>> Ilya, > > >>> > > >>> Thanks for catching that and sharing. I wonder if there are any other > > >>> blockers that were pushed to 2.8.x version. If there are a few then > we > > >> can > > >>> produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix > the > > >>> issue with putAll, update the binaries and finish the process. > > >>> > > >>> - > > >>> Denis > > >>> > > >>> > > >>> On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev < > > >> ilya.kasnach...@gmail.com> > > >>> wrote: > > >>> > > Hello! > > > > I have filed an issue > > >> https://issues.apache.org/jira/browse/IGNITE-12746 > > > > I think this is potentially a game breaker and makes me recommend > > >> avoiding > > 2.8, if we release it without fix (for now). > > > > If you are using any partitioned caches, anyway. > > > > So I suggest we withhold 2.8. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov : > > > > > Ilya, > > > > > > I do not want to force the release no matter what happens, but I > > think > > > we should release what we have to get feedback not just from the > > > developer community but from our users too. > > > > > > And fix all these issues in 2.8.1. > > > > > > On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev < > > >> ilya.kasnach...@gmail.com> > > > wrote: > > >> > > >> Hello! > > >> > > >> Can we please hold back publishing AI-2.8.0-rc1 as public Apache > > >> Ignite > > > 2.8 > > >> release? > > >> > > >> I have just been notified that > > >> > > > > > > > >> > > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated > > >> > > > > > > > >> > > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed > > >> are flaky: they seem to deadlock on putAll sorted keys maps. They > > used > > to > > >> pass solidly on 2.7, but fail on master and ignite-2.8. > > >> > > >> (They fail around 1 time out of 10, so just run them 25 times to > > >> check) > > >> > > >> If there is indeed a deadlock, this would become a blocker to this > > > release, > > >> in my opinion, but I need some time to check. > > >> > > >> Regards, > > >> -- > > >> Ilya Kasnacheev > > >> > > >> > > >> вс, 1 мар. 2020 г. в 11:29, Maxim Muzafarov : > > >> > > >>> Ivan, > > >>> > > >>> > > >>> I agree with you that the more members will check the release the > > >>> better will be. That's why I've shared the release candidate > links > > [1] > > >>> before starting a vote. The best time for starting a vote is not > > >>> mentioned at our release wiki page [2] (should we?) and I've also > > >>> failed with googling the best practices for it too. So, I've > > supposed > > >>> since all of us are working on their own tasks during weekdays > the > > >>> free time on the weekend is the best choice for cheking\voting on > > the > > >>>
Re: Ignite 2.8 documentation
> > I'll work on the following items today and tomorrow: > >- JDBC: Support for query cancellation > > >- JDBC: Support for query timeout > > >- suspend/resume for pessimistic transactions > > >- WAL page compression > > Artem, are these the only tickets left apart from the metrics & monitoring? @Nikolay Izhikov how soon will you be able to finish the metrics documentation pages? - Denis On Wed, Mar 4, 2020 at 2:55 AM Artem Budnikov wrote: > Hi everyone, > > I have created the docs for the following items so far: > >-Default Ignite work dir location > > > https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory > >- Baseline auto-adjust feature > > > https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment > >- Cluster (de)activation events documentation > > > https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events > >- Remove SqlQuery documentation >done > >- Partition awareness for thin clients > > > https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness > > > https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness > >- Transactions support in java thin client > > > https://apacheignite.readme.io/docs/key-value-28#section-client-transactions > >- KILL QUERY command > >https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query > >- Move rebalance configuration properties to the >IgniteConfiguration level > > > https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration > >- Renamed IGNITE schema to SYS >done > > I'll work on the following items today and tomorrow: > >- JDBC: Support for query cancellation >- JDBC: Support for query timeout >- suspend/resume for pessimistic transactions >- WAL page compression > > > Nikolay, > > How is your progress with the Metrics and System Views documentation? > > > Artem Budnikov > Technical Writergridgain.com > > On 03.03.2020 19:06, Maxim Muzafarov wrote: > > Folks, > > This is in the `Ignite Core` section, so I think mostly related to > java functionality and thin client protocol extension [1]. Sorry for > not being too accurate with this statement > . > The same change is mentioned for C++ and .NET sections of the release > notes (but not for other thin clients). > > > [1] https://issues.apache.org/jira/browse/IGNITE-11898 > > On Tue, 3 Mar 2020 at 17:33, Igor Sapego > wrote: > > That's right, only C++ and .NET clients have partition awareness > > Best Regards, > Igor > > > On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov > > wrote: > > > Hi everyone, > > Looks like the following line from the Ignite 2.8 release notes is a bit > of an overstatement and should be removed: > > > Added support best effort affinity for thin clients (partition awareness) > > Java thin client does not support partition awareness. Nodejs and python > thin clients from the distribution package do not have signs of this > feature as well. > > Igor, > > Could you please confirm or deny this? > > -Artem > > Artem Budnikov > Technical Writergridgain.com > > On 03.03.2020 01:47, Denis Magda wrote: > > Hi Alexey, > > Thanks for updating the documentation. The update process is cumbersome as > of now. What will happen is that we will be replacing the content of the > current pages (pre 2.8 pages) with the content from the 2.8 versions. Once > the text is copied manually, a 2.8 version of the page will be deleted. I > would advise Artem to do that this time and update the wiki page with more > details:https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document > > Also, why should we release this > page?https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms > > - > Denis > > > On Sun, Mar 1, 2020 at 7:59 AM Alexey Zinoviev > > wrote: > > > Hi, Igniters, I've finished the ML documentation. > > I have the issue that, for example I've created a new version of page with > postfix -2.8 and the page name contains this postfix. > How are we going to replace the URL? Or we will replace the content from > initial page? > > For example, I've created the new version of > pagehttps://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees > and > moved it under new > pagehttps://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees-28 > How it will be processed to obtain the decision-trees url for the new > page? > > > In all case the full list of removed/replaced pages for ML is next: > > In the release 2.8, please remove the pages > >1. > https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms > >2. > https://dash.readme.io/project/apacheignite/v2.7.6/docs/svm-multi-class-classification > >3. DeepLearning block with 3 pages >4.
Re: Ignite 2.8 documentation
Artem, IEP [1] answers this in detail, but in brief... Cons: - each get() cost, when RR used, increased by requests to each backup, - read from backup, near cache and external store usage are impossible. Pros: - consistency may be checked online (no need to turn off the cluster), - consistency will be recovered in necessary for transactional caches. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-31+Consistency+check+and+fix On Wed, Mar 4, 2020 at 3:20 PM Artem Budnikov wrote: > Anton, > > Yes, I can add this feature to the docs. I have a couple of questions, > though: > > * Are there any downsides to using this feature? > * When users should use it? What are the recommendations? > > > -Artem > > On 04.03.2020 13:46, Anton Vinogradov wrote: > > Artem, > > Is it possible to create documentation for ReadRepair feature [1] [2]? > > Feature marked as @IgnireExperimenta but ready to be used. > > Javadoc [3] explains the details. > > > > [1] > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-31+Consistency+check+and+fix > > [2] https://issues.apache.org/jira/browse/IGNITE-10663 > > [3] https://issues.apache.org/jira/browse/IGNITE-11978 > > > > On Wed, Mar 4, 2020 at 1:15 PM Artem Budnikov > > wrote: > > > >> Hi everyone, > >> > >> I have created the docs for the following items so far: > >> > >>* Default Ignite work dir location > >> > >> > https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory > >> > >> > >>* Baseline auto-adjust feature > >> > >> > https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment > >> > >>* Cluster (de)activation events documentation > >> > >> > https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events > >> > >>* Remove SqlQuery documentation > >> done > >> > >>* Partition awareness for thin clients > >> > >> > https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness > >> > >> > >> > https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness > >> > >>* Transactions support in java thin client > >> > >> > https://apacheignite.readme.io/docs/key-value-28#section-client-transactions > >> > >> > >>* KILL QUERY command > >> > https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query > >> > >>* Move rebalance configuration properties to the > >> IgniteConfiguration level > >> > >> > https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration > >> > >>* Renamed IGNITE schema to SYS > >> done > >> > >> I'll work on the following items today and tomorrow: > >> > >>* JDBC: Support for query cancellation > >>* JDBC: Support for query timeout > >>* suspend/resume for pessimistic transactions > >>* WAL page compression > >> > >> > >> Nikolay, > >> > >> How is your progress with the Metrics and System Views documentation? > >> > >> > >> Artem Budnikov > >> Technical Writer > >> gridgain.com > >> > >> On 03.03.2020 19:06, Maxim Muzafarov wrote: > >>> Folks, > >>> > >>> This is in the `Ignite Core` section, so I think mostly related to > >>> java functionality and thin client protocol extension [1]. Sorry for > >>> not being too accurate with this statement > >>> . > >>> The same change is mentioned for C++ and .NET sections of the release > >>> notes (but not for other thin clients). > >>> > >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-11898 > >>> > >>> On Tue, 3 Mar 2020 at 17:33, Igor Sapego wrote: > That's right, only C++ and .NET clients have partition awareness > > Best Regards, > Igor > > > On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov > > wrote: > > > Hi everyone, > > > > Looks like the following line from the Ignite 2.8 release notes is a > >> bit > > of an overstatement and should be removed: > > > >> Added support best effort affinity for thin clients (partition > >> awareness) > > Java thin client does not support partition awareness. Nodejs and > >> python > > thin clients from the distribution package do not have signs of this > > feature as well. > > > > Igor, > > > > Could you please confirm or deny this? > > > > -Artem > > > > Artem Budnikov > > Technical Writergridgain.com > > > > On 03.03.2020 01:47, Denis Magda wrote: > > > > Hi Alexey, > > > > Thanks for updating the documentation. The update process is > >> cumbersome as > > of now. What will happen is that we will be replacing the content of > >> the > > current pages (pre 2.8 pages) with the content from the 2.8 versions. > >> Once > > the text is copied manually, a 2.8 version of the page will be > >> deleted. I > > would advise Artem to do that this time and update the wiki page with >
Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Hello! Thank you for leading this discussion. I agree with some other voices that we should never start voting about new release over the weekend. I think that only monday and tuesday are suitable for new release votings, since it guarantees that announcement, voting and decision all happen on week days. However, in this case it would not help. The bug was introduced almost half year ago and was found entirely by chance, not related to release procedures or voting. It is just a coincidence that I found out about it simultaneously with release roll-over. I agree that we should target 2.8.1 now. Regards, -- Ilya Kasnacheev ср, 4 мар. 2020 г. в 15:40, Dmitriy Pavlov : > Ilya, let me personally thank you for checking and filing this bug. > > I checked timeline for [result] [vote] email and new email describing new > issue. Unfortunately, after closing the vote it is not possible to stop > release from publishing (only if RM will delay publish stage after closing > the vote). In this case publishing already happened, so replacing existing > binary with new one can cause a lot of mess. > > What do you think about our future steps to learn from this case? It is > possible to keep vote open longer that 72hours if someone is still checking > things. Would it help if we agree on RM will delay closing the voting > process until all interested participants finish their checks? > > Sincerely, > Dmitriy Pavlov > > вт, 3 мар. 2020 г. в 20:33, Ilya Kasnacheev : > > > Hello! > > > > Can we please hold back publishing AI-2.8.0-rc1 as public Apache Ignite > 2.8 > > release? > > > > I have just been notified that > > > > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated > > > > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed > > are flaky: they seem to deadlock on putAll sorted keys maps. They used to > > pass solidly on 2.7, but fail on master and ignite-2.8. > > > > (They fail around 1 time out of 10, so just run them 25 times to check) > > > > If there is indeed a deadlock, this would become a blocker to this > release, > > in my opinion, but I need some time to check. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вс, 1 мар. 2020 г. в 11:29, Maxim Muzafarov : > > > > > Ivan, > > > > > > > > > I agree with you that the more members will check the release the > > > better will be. That's why I've shared the release candidate links [1] > > > before starting a vote. The best time for starting a vote is not > > > mentioned at our release wiki page [2] (should we?) and I've also > > > failed with googling the best practices for it too. So, I've supposed > > > since all of us are working on their own tasks during weekdays the > > > free time on the weekend is the best choice for cheking\voting on the > > > release. Probably this decision was wrong. > > > > > > [1] > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-tp43616p46117.html > > > [2] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > > > > > On Sun, 1 Mar 2020 at 00:37, Ivan Pavlukhin > wrote: > > > > > > > > Also I have a comment regarding to voting. Voting for 72 hour > spanning > > > > a weekend sounds a little bit odd to me. In a particular case the > more > > > > people check the release the better. And I suppose there is more time > > > > for it on weekdays for the majority. > > > > > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > вс, 1 мар. 2020 г. в 00:33, Ivan Pavlukhin : > > > > > > > > > > > As I remember, that Pavlov suggested to discuss threats on a > > private > > > PMC list > > > > > Cannot understand why it should be discussed on a private list. > What > > > > > is the clue? > > > > > > > > > > Best regards, > > > > > Ivan Pavlukhin > > > > > > > > > > сб, 29 февр. 2020 г. в 16:00, Alexey Zinoviev < > > zaleslaw@gmail.com > > > >: > > > > > > > > > > > > As I remember, that Pavlov suggested to discuss threats on a > > private > > > PMC > > > > > > list > > > > > > > > > > > > сб, 29 февр. 2020 г., 15:12 Ilya Kasnacheev < > > > ilya.kasnach...@gmail.com>: > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > As far as my understanding goes, ignite-zookeeper is listed for > > > removal > > > > > > > because it brings a lot of dependencies, some of which may have > > > known > > > > > > > vulnerabilities, which will make the distribution also > considered > > > > > > > vulnerable by some scanners. > > > > > > > > > > > > > > Regards, > > > > > > > -- > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > сб, 29 февр. 2020 г. в 14:18, Alexey Zinoviev < > > > zaleslaw@gmail.com>: > > > > > > > > > > > > > > > Ok, lets move to this thread. Also, the slim release could be > > > form by > > > > > > > > voting on user-list > > > > > > > > > > > > > > > > сб, 29 февр. 2020 г., 9:55
Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Ilya, let me personally thank you for checking and filing this bug. I checked timeline for [result] [vote] email and new email describing new issue. Unfortunately, after closing the vote it is not possible to stop release from publishing (only if RM will delay publish stage after closing the vote). In this case publishing already happened, so replacing existing binary with new one can cause a lot of mess. What do you think about our future steps to learn from this case? It is possible to keep vote open longer that 72hours if someone is still checking things. Would it help if we agree on RM will delay closing the voting process until all interested participants finish their checks? Sincerely, Dmitriy Pavlov вт, 3 мар. 2020 г. в 20:33, Ilya Kasnacheev : > Hello! > > Can we please hold back publishing AI-2.8.0-rc1 as public Apache Ignite 2.8 > release? > > I have just been notified that > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated > > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed > are flaky: they seem to deadlock on putAll sorted keys maps. They used to > pass solidly on 2.7, but fail on master and ignite-2.8. > > (They fail around 1 time out of 10, so just run them 25 times to check) > > If there is indeed a deadlock, this would become a blocker to this release, > in my opinion, but I need some time to check. > > Regards, > -- > Ilya Kasnacheev > > > вс, 1 мар. 2020 г. в 11:29, Maxim Muzafarov : > > > Ivan, > > > > > > I agree with you that the more members will check the release the > > better will be. That's why I've shared the release candidate links [1] > > before starting a vote. The best time for starting a vote is not > > mentioned at our release wiki page [2] (should we?) and I've also > > failed with googling the best practices for it too. So, I've supposed > > since all of us are working on their own tasks during weekdays the > > free time on the weekend is the best choice for cheking\voting on the > > release. Probably this decision was wrong. > > > > [1] > > > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-tp43616p46117.html > > [2] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > > > On Sun, 1 Mar 2020 at 00:37, Ivan Pavlukhin wrote: > > > > > > Also I have a comment regarding to voting. Voting for 72 hour spanning > > > a weekend sounds a little bit odd to me. In a particular case the more > > > people check the release the better. And I suppose there is more time > > > for it on weekdays for the majority. > > > > > > Best regards, > > > Ivan Pavlukhin > > > > > > вс, 1 мар. 2020 г. в 00:33, Ivan Pavlukhin : > > > > > > > > > As I remember, that Pavlov suggested to discuss threats on a > private > > PMC list > > > > Cannot understand why it should be discussed on a private list. What > > > > is the clue? > > > > > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > сб, 29 февр. 2020 г. в 16:00, Alexey Zinoviev < > zaleslaw@gmail.com > > >: > > > > > > > > > > As I remember, that Pavlov suggested to discuss threats on a > private > > PMC > > > > > list > > > > > > > > > > сб, 29 февр. 2020 г., 15:12 Ilya Kasnacheev < > > ilya.kasnach...@gmail.com>: > > > > > > > > > > > Hello! > > > > > > > > > > > > As far as my understanding goes, ignite-zookeeper is listed for > > removal > > > > > > because it brings a lot of dependencies, some of which may have > > known > > > > > > vulnerabilities, which will make the distribution also considered > > > > > > vulnerable by some scanners. > > > > > > > > > > > > Regards, > > > > > > -- > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > сб, 29 февр. 2020 г. в 14:18, Alexey Zinoviev < > > zaleslaw@gmail.com>: > > > > > > > > > > > > > Ok, lets move to this thread. Also, the slim release could be > > form by > > > > > > > voting on user-list > > > > > > > > > > > > > > сб, 29 февр. 2020 г., 9:55 Alexey Goncharuk < > > alexey.goncha...@gmail.com > > > > > > >: > > > > > > > > > > > > > > > Nikolay, Alexey, > > > > > > > > > > > > > > > > First, the idea of the slim binary release and docker image > was > > > > > > discussed > > > > > > > > openly on the dev-list [1]. Second, nobody talks about > > removing these > > > > > > > > modules from the product. The idea was to create an > additional > > > > > > > distribution > > > > > > > > which is much lighter than the current full package to reduce > > the size > > > > > > of > > > > > > > > the downloadable artifact and reduce the number of potential > > > > > > > > vulnerabilities in third-party libraries. > > > > > > > > > > > > > > > > The list of modules was chosen subjectively by the number of > > questions > > > > > > on > > > > > > > > the user-list, number third-party libraries (size) and > > vulnerabilities > > > > > > > the > > > > > > > > module
Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Hi Folks, Unfortunately https://dist.apache.org/repos/dist/release/ignite/2.8.0/ is already there, so release was happened. I'm not sure it is a good idea to substitute binaries later. Was it announced to announce@ ? IMO, 2.8.1 is ok for that case. Sincerely, Dmitriy Pavlov ср, 4 мар. 2020 г. в 11:29, Nikolay Izhikov : > Pavel, ++1. > > > 4 марта 2020 г., в 11:20, Pavel Tupitsyn > написал(а): > > > > Igniters, > > > > The release has already happened. > > It is on our website [1], it is on Maven [2]. > > People are using it, so I don't think we can do anything at this point. > > > > Bugs happen, we can't delay the release forever because of them. Let's > fix > > things in 2.8.1. > > > > [1] https://ignite.apache.org/download.cgi > > [2] https://mvnrepository.com/artifact/org.apache.ignite > > > > > > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov > wrote: > > > >> Hello, Igniters. > >> > >> Do we have a person who can fix this issue in the nearest time? > >> Right now IGNITE-12746 is Open and Unassigned. > >> > >>> 3 марта 2020 г., в 23:54, Denis Magda написал(а): > >>> > >>> Ilya, > >>> > >>> Thanks for catching that and sharing. I wonder if there are any other > >>> blockers that were pushed to 2.8.x version. If there are a few then we > >> can > >>> produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix the > >>> issue with putAll, update the binaries and finish the process. > >>> > >>> - > >>> Denis > >>> > >>> > >>> On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev < > >> ilya.kasnach...@gmail.com> > >>> wrote: > >>> > Hello! > > I have filed an issue > >> https://issues.apache.org/jira/browse/IGNITE-12746 > > I think this is potentially a game breaker and makes me recommend > >> avoiding > 2.8, if we release it without fix (for now). > > If you are using any partitioned caches, anyway. > > So I suggest we withhold 2.8. > > Regards, > -- > Ilya Kasnacheev > > > вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov : > > > Ilya, > > > > I do not want to force the release no matter what happens, but I > think > > we should release what we have to get feedback not just from the > > developer community but from our users too. > > > > And fix all these issues in 2.8.1. > > > > On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev < > >> ilya.kasnach...@gmail.com> > > wrote: > >> > >> Hello! > >> > >> Can we please hold back publishing AI-2.8.0-rc1 as public Apache > >> Ignite > > 2.8 > >> release? > >> > >> I have just been notified that > >> > > > > >> > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated > >> > > > > >> > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed > >> are flaky: they seem to deadlock on putAll sorted keys maps. They > used > to > >> pass solidly on 2.7, but fail on master and ignite-2.8. > >> > >> (They fail around 1 time out of 10, so just run them 25 times to > >> check) > >> > >> If there is indeed a deadlock, this would become a blocker to this > > release, > >> in my opinion, but I need some time to check. > >> > >> Regards, > >> -- > >> Ilya Kasnacheev > >> > >> > >> вс, 1 мар. 2020 г. в 11:29, Maxim Muzafarov : > >> > >>> Ivan, > >>> > >>> > >>> I agree with you that the more members will check the release the > >>> better will be. That's why I've shared the release candidate links > [1] > >>> before starting a vote. The best time for starting a vote is not > >>> mentioned at our release wiki page [2] (should we?) and I've also > >>> failed with googling the best practices for it too. So, I've > supposed > >>> since all of us are working on their own tasks during weekdays the > >>> free time on the weekend is the best choice for cheking\voting on > the > >>> release. Probably this decision was wrong. > >>> > >>> [1] > >>> > > > > >> > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-tp43616p46117.html > >>> [2] > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > >>> > >>> On Sun, 1 Mar 2020 at 00:37, Ivan Pavlukhin > > wrote: > > Also I have a comment regarding to voting. Voting for 72 hour > > spanning > a weekend sounds a little bit odd to me. In a particular case the > > more > people check the release the better. And I suppose there is more > time > for it on weekdays for the majority. > > Best regards, > Ivan Pavlukhin > > вс, 1 мар. 2020 г. в 00:33, Ivan Pavlukhin : > > > >> As I remember, that Pavlov
Re: Ignite 2.8 documentation
Anton, Yes, I can add this feature to the docs. I have a couple of questions, though: * Are there any downsides to using this feature? * When users should use it? What are the recommendations? -Artem On 04.03.2020 13:46, Anton Vinogradov wrote: Artem, Is it possible to create documentation for ReadRepair feature [1] [2]? Feature marked as @IgnireExperimenta but ready to be used. Javadoc [3] explains the details. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-31+Consistency+check+and+fix [2] https://issues.apache.org/jira/browse/IGNITE-10663 [3] https://issues.apache.org/jira/browse/IGNITE-11978 On Wed, Mar 4, 2020 at 1:15 PM Artem Budnikov wrote: Hi everyone, I have created the docs for the following items so far: * Default Ignite work dir location https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory * Baseline auto-adjust feature https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment * Cluster (de)activation events documentation https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events * Remove SqlQuery documentation done * Partition awareness for thin clients https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness * Transactions support in java thin client https://apacheignite.readme.io/docs/key-value-28#section-client-transactions * KILL QUERY command https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query * Move rebalance configuration properties to the IgniteConfiguration level https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration * Renamed IGNITE schema to SYS done I'll work on the following items today and tomorrow: * JDBC: Support for query cancellation * JDBC: Support for query timeout * suspend/resume for pessimistic transactions * WAL page compression Nikolay, How is your progress with the Metrics and System Views documentation? Artem Budnikov Technical Writer gridgain.com On 03.03.2020 19:06, Maxim Muzafarov wrote: Folks, This is in the `Ignite Core` section, so I think mostly related to java functionality and thin client protocol extension [1]. Sorry for not being too accurate with this statement . The same change is mentioned for C++ and .NET sections of the release notes (but not for other thin clients). [1] https://issues.apache.org/jira/browse/IGNITE-11898 On Tue, 3 Mar 2020 at 17:33, Igor Sapego wrote: That's right, only C++ and .NET clients have partition awareness Best Regards, Igor On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov wrote: Hi everyone, Looks like the following line from the Ignite 2.8 release notes is a bit of an overstatement and should be removed: Added support best effort affinity for thin clients (partition awareness) Java thin client does not support partition awareness. Nodejs and python thin clients from the distribution package do not have signs of this feature as well. Igor, Could you please confirm or deny this? -Artem Artem Budnikov Technical Writergridgain.com On 03.03.2020 01:47, Denis Magda wrote: Hi Alexey, Thanks for updating the documentation. The update process is cumbersome as of now. What will happen is that we will be replacing the content of the current pages (pre 2.8 pages) with the content from the 2.8 versions. Once the text is copied manually, a 2.8 version of the page will be deleted. I would advise Artem to do that this time and update the wiki page with more details: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document Also, why should we release this page? https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms - Denis On Sun, Mar 1, 2020 at 7:59 AM Alexey Zinoviev Hi, Igniters, I've finished the ML documentation. I have the issue that, for example I've created a new version of page with postfix -2.8 and the page name contains this postfix. How are we going to replace the URL? Or we will replace the content from initial page? For example, I've created the new version of page https://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees and moved it under new page https://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees-28 How it will be processed to obtain the decision-trees url for the new page? In all case the full list of removed/replaced pages for ML is next: In the release 2.8, please remove the pages 1. https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms 2. https://dash.readme.io/project/apacheignite/v2.7.6/docs/svm-multi-class-classification 3. DeepLearning block with 3 pages 4.
Re: [RESULT] [VOTE] Release Apache Ignite 2.8.0 RC1
GCE image is broken but it is a "know issue" and will be fixed some time later. AWS image is self sufficient — no additional steps required to run Apache Ignite 2.8.0 on AWS using it. > On 4 Mar 2020, at 14:08, Maxim Muzafarov wrote: > > Pavel, Pert, Nikolay, > > > Thank you all for your help. I stuck yesterday due to don't have > sufficient privileges to complete some of the release steps. > Currently, all of them have been completed. > > Do I need something to do with these additional steps? > > AWS deployment -- > https://console.aws.amazon.com/ec2/home?region=eu-central-1#launchAmi=ami-191b0775 > GCE deployment -- https://console.cloud.google.com/compute/images > > > On Wed, 4 Mar 2020 at 12:22, Petr Ivanov wrote: >> >> Docker image uploaded. >> >> >>> On 4 Mar 2020, at 11:37, Pavel Tupitsyn wrote: >>> >>> Maxim, what about the rest of the release steps, like Docker and NuGet? Do >>> you need help with that? >>> >>> On Wed, Mar 4, 2020 at 9:33 AM Alexey Zinoviev >>> wrote: >>> Maxim, you great, I was happy to work with you on that release, it was a very difficult task and it required a lot of your time, thank you ср, 4 мар. 2020 г., 8:46 Anton Vinogradov : > Awesome! > Thanks for leading this. > > BTW, do we have plans to start 2.9 release process in nearest future? > > On Tue, Mar 3, 2020 at 11:07 PM Maxim Muzafarov wrote: > >> Folks, >> >> >> I've done (with Santa's help) most of the steps related to the 2.8.0 >> RELEASE. >> Here are some links according to accepted the release candidate. >> >> >> Binary, Sources: >> https://dist.apache.org/repos/dist/release/ignite/2.8.0/ >> >> Bintray: >> https://bintray.com/apache/ignite-rpm/apache-ignite/2.8.0 >> https://bintray.com/apache/ignite-deb/apache-ignite/2.8.0 >> >> Javadocs: >> https://svn.apache.org/repos/asf/ignite/site/trunk/releases/2.8.0/ >> >> RELEASE_NOTES: >> >> > https://svn.apache.org/repos/asf/ignite/site/trunk/releases/2.8.0/release_notes.html >> >> git tag: >> >> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=341b01dfd8abf2d9b01d468ad1bb26dfe84ac4f6 >> >> Download links: >> https://ignite.apache.org/download.cgi >> >> On Mon, 2 Mar 2020 at 22:10, Maxim Muzafarov wrote: >>> >>> Dear community, >>> >>> >>> The vote for a new release candidate is closed, now. >>> Vote result: The vote PASSES with 6 votes +1 (6 bindings), 0 two votes >>> and no -1. >>> >>> >>> +1 votes: >>> - Denis Magda (binding) >>> - Anton Vinogradov (binding) >>> - Pavel Tupitsyn (binding) >>> - Ivan Pavlukhin (binding) >>> - Alexey Zinoviev (binding) >>> - Nikolay Izhikov (binding) >>> >>> 0 votes: >>> - Ilya Kasnacheev (binding) >>> - Sergey Antonov >>> >>> >>> Vote thread: >>> >> > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Release-Apache-Ignite-2-8-0-RC1-td46140.html >> > >>
[jira] [Created] (IGNITE-12747) Calcite integration. Correlated queries support.
Igor Seliverstov created IGNITE-12747: - Summary: Calcite integration. Correlated queries support. Key: IGNITE-12747 URL: https://issues.apache.org/jira/browse/IGNITE-12747 Project: Ignite Issue Type: New Feature Reporter: Igor Seliverstov -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Configuring Ignite Thread Pool's Core thread count/max thread count/etc
Hello! My opinion is that we have what we have and I recommend using the API provided with Apache Ignite. Regards, -- Ilya Kasnacheev чт, 27 февр. 2020 г. в 13:57, Sunny Chan, CLSA : > Just to make it clear, you prefer the option 1 in my suggestion? That is > listed out all the potential configurable for thread pool for each thread > pools in Ignite? > > > > I do see that we have setDataStorageConfiguration where the parameters for > data storage is grouped together into a configuration object, similar to my > proposal 2 –would that be better? > > > > *From:* Ilya Kasnacheev > *Sent:* Thursday, February 27, 2020 6:05 PM > *To:* Sunny Chan, CLSA > *Cc:* dev > *Subject:* Re: Configuring Ignite Thread Pool's Core thread count/max > thread count/etc > > > > Hello! > > > > My suggestion is to use > org.apache.ignite.configuration.IgniteConfiguration and avoid introducing > your own classes, etc. Cut out the middle man. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > чт, 27 февр. 2020 г. в 05:36, Sunny Chan, CLSA : > > Hi Ilya, > > For the IgniteConfiguration interface, do we prefer: > > 1) IgniteConfiguration.setSystemThreadPoolCoreSize(), > IgniteConfiguration.setSystemThreadPoolTimeOut(),IgniteConfiguration.setPublicThreadPoolCoreSize(), > etc. > 2) IgniteConfiguration.setSystemThreadPool(ThreadPoolConfiguration), > IgniteConfiguration.setThreadPoolCoreSize(ThreadPoolConfiguration) and then > we have ThreadPoolConfiguration.setCoreSize(), etc > > Thanks. > > -Original Message- > From: Ilya Kasnacheev > Sent: Wednesday, February 26, 2020 6:10 PM > To: dev > Subject: Re: Configuring Ignite Thread Pool's Core thread count/max thread > count/etc > > Hello! > > We recommend exposing IgniteConfiguration for user to modify. You never > know in advance what kind of tuning will be needed, and don't want to play > chinese whispers game with your users. > > Regards, > -- > Ilya Kasnacheev > > > ср, 26 февр. 2020 г. в 13:07, Sunny Chan, CLSA : > > > Hello, > > > > > > > > We are running Ignite cluster on bare metal on a relatively high core > > count machine (4x10 cores 20 threads), and looking some of the thread > pool > > initialization code: > > > > > > > > (IgnitionEx.java) > > > > sysExecSvc = *new* IgniteThreadPoolExecutor( > > > > "sys", > > > > cfg.getIgniteInstanceName(), > > > > cfg.getSystemThreadPoolSize(), > > > > cfg.getSystemThreadPoolSize(), > > > > *DFLT_THREAD_KEEP_ALIVE_TIME*, > > > > *new* LinkedBlockingQueue(), > > > > GridIoPolicy.*SYSTEM_POOL*); > > > > > > > > Notice that the core thread pool size is equals to the max thread pool > > settings, which is by default same as the number of CPU cores. And in our > > cases, we won’t be reusing any threads until we have enough request > coming > > in to fill 80 threads. Also, we might want to tune the thread keep alive > > time to improve thread reuse. > > > > > > > > We would like to propose to change ignite so that users can configure the > > core thread pool size in these Ignite thread pools. What is the best way > to > > expose these parameters for user to modify? > > > > > > > > Would the ignite dev team prefer exposing individual core thread size and > > others (ie. cfg.get/setSystemThreadPoolCoreSize(), > > cfg.get/setSystemThreadPoolKeepAliveTime(), ..) or should we use a thread > > pool configuration object? (e.g. > > cfg.getSystemThreadPoolConfiguration(ThreadPoolConfiguration config) > where > > ThreadPoolConfiguration has get and set methods for core thread pool > size, > > etc)? > > > > > > > > *Sunny Chan* > > > > *Senior Lead Engineer, Executive Services* > > > > D +852 2600 8907 | M +852 6386 1835 | T +852 2600 > > > > 5/F, One Island East, 18 Westlands Road, Island East, Hong Kong > > > > > > > > [image: :1. Social Media Icons:CLSA_Social Media Icons_linkedin.png] > > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__hk.linkedin.com_company_clsa=DwIFaQ=lxzXOFU02467FL7HOPRqCw=9dPMIMeLdcqo3dX29zZZ4USXrC7gp_0p-Fvzzp2WzgU=cblNaj4j3LVM7Djyn0ffKyR3bThUEDp7iqqm5mRgkys=Yaq04TdZjYF0IXiRHXdbJS_fU_YNho-DXGuYjRNAfRM= > >[image: :1. Social Media > > Icons:CLSA_Social Media Icons_twitter.png] > > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_clsainsights-3Flang-3Den=DwIFaQ=lxzXOFU02467FL7HOPRqCw=9dPMIMeLdcqo3dX29zZZ4USXrC7gp_0p-Fvzzp2WzgU=cblNaj4j3LVM7Djyn0ffKyR3bThUEDp7iqqm5mRgkys=60dVf5GhkOQ8CsuUVPmzqzQ3KBWI7Jl66i-gAajMqhw= > >[image: :1. Social Media > > Icons:CLSA_Social Media Icons_youtube.png] > > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_channel_UC0qWp-5FlLnOcRYmBlCNQgZKA=DwIFaQ=lxzXOFU02467FL7HOPRqCw=9dPMIMeLdcqo3dX29zZZ4USXrC7gp_0p-Fvzzp2WzgU=cblNaj4j3LVM7Djyn0ffKyR3bThUEDp7iqqm5mRgkys=mDwljLI4KYkfMCIaiGVeezUNf52sbK8OLOj90ISnrOU= > >[image: :1. > > Social Media Icons:CLSA_Social Media Icons_facebook.png] > > < >
Re: [RESULT] [VOTE] Release Apache Ignite 2.8.0 RC1
Pavel, Pert, Nikolay, Thank you all for your help. I stuck yesterday due to don't have sufficient privileges to complete some of the release steps. Currently, all of them have been completed. Do I need something to do with these additional steps? AWS deployment -- https://console.aws.amazon.com/ec2/home?region=eu-central-1#launchAmi=ami-191b0775 GCE deployment -- https://console.cloud.google.com/compute/images On Wed, 4 Mar 2020 at 12:22, Petr Ivanov wrote: > > Docker image uploaded. > > > > On 4 Mar 2020, at 11:37, Pavel Tupitsyn wrote: > > > > Maxim, what about the rest of the release steps, like Docker and NuGet? Do > > you need help with that? > > > > On Wed, Mar 4, 2020 at 9:33 AM Alexey Zinoviev > > wrote: > > > >> Maxim, you great, I was happy to work with you on that release, it was a > >> very difficult task and it required a lot of your time, thank you > >> > >> ср, 4 мар. 2020 г., 8:46 Anton Vinogradov : > >> > >>> Awesome! > >>> Thanks for leading this. > >>> > >>> BTW, do we have plans to start 2.9 release process in nearest future? > >>> > >>> On Tue, Mar 3, 2020 at 11:07 PM Maxim Muzafarov > >> wrote: > >>> > Folks, > > > I've done (with Santa's help) most of the steps related to the 2.8.0 > RELEASE. > Here are some links according to accepted the release candidate. > > > Binary, Sources: > https://dist.apache.org/repos/dist/release/ignite/2.8.0/ > > Bintray: > https://bintray.com/apache/ignite-rpm/apache-ignite/2.8.0 > https://bintray.com/apache/ignite-deb/apache-ignite/2.8.0 > > Javadocs: > https://svn.apache.org/repos/asf/ignite/site/trunk/releases/2.8.0/ > > RELEASE_NOTES: > > > >>> > >> https://svn.apache.org/repos/asf/ignite/site/trunk/releases/2.8.0/release_notes.html > > git tag: > > > >>> > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=341b01dfd8abf2d9b01d468ad1bb26dfe84ac4f6 > > Download links: > https://ignite.apache.org/download.cgi > > On Mon, 2 Mar 2020 at 22:10, Maxim Muzafarov > >> wrote: > > > > Dear community, > > > > > > The vote for a new release candidate is closed, now. > > Vote result: The vote PASSES with 6 votes +1 (6 bindings), 0 two > >> votes > > and no -1. > > > > > > +1 votes: > > - Denis Magda (binding) > > - Anton Vinogradov (binding) > > - Pavel Tupitsyn (binding) > > - Ivan Pavlukhin (binding) > > - Alexey Zinoviev (binding) > > - Nikolay Izhikov (binding) > > > > 0 votes: > > - Ilya Kasnacheev (binding) > > - Sergey Antonov > > > > > > Vote thread: > > > > >>> > >> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Release-Apache-Ignite-2-8-0-RC1-td46140.html > > >>> > >> >
Re: Ignite 2.8 documentation
Artem, Is it possible to create documentation for ReadRepair feature [1] [2]? Feature marked as @IgnireExperimenta but ready to be used. Javadoc [3] explains the details. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-31+Consistency+check+and+fix [2] https://issues.apache.org/jira/browse/IGNITE-10663 [3] https://issues.apache.org/jira/browse/IGNITE-11978 On Wed, Mar 4, 2020 at 1:15 PM Artem Budnikov wrote: > Hi everyone, > > I have created the docs for the following items so far: > > * Default Ignite work dir location > > https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory > > > * Baseline auto-adjust feature > > https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment > > * Cluster (de)activation events documentation > > https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events > > * Remove SqlQuery documentation > done > > * Partition awareness for thin clients > > https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness > > > https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness > > * Transactions support in java thin client > > https://apacheignite.readme.io/docs/key-value-28#section-client-transactions > > > * KILL QUERY command > https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query > > * Move rebalance configuration properties to the > IgniteConfiguration level > > https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration > > * Renamed IGNITE schema to SYS > done > > I'll work on the following items today and tomorrow: > > * JDBC: Support for query cancellation > * JDBC: Support for query timeout > * suspend/resume for pessimistic transactions > * WAL page compression > > > Nikolay, > > How is your progress with the Metrics and System Views documentation? > > > Artem Budnikov > Technical Writer > gridgain.com > > On 03.03.2020 19:06, Maxim Muzafarov wrote: > > Folks, > > > > This is in the `Ignite Core` section, so I think mostly related to > > java functionality and thin client protocol extension [1]. Sorry for > > not being too accurate with this statement > > . > > The same change is mentioned for C++ and .NET sections of the release > > notes (but not for other thin clients). > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11898 > > > > On Tue, 3 Mar 2020 at 17:33, Igor Sapego wrote: > >> That's right, only C++ and .NET clients have partition awareness > >> > >> Best Regards, > >> Igor > >> > >> > >> On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov > >> wrote: > >> > >>> Hi everyone, > >>> > >>> Looks like the following line from the Ignite 2.8 release notes is a > bit > >>> of an overstatement and should be removed: > >>> > Added support best effort affinity for thin clients (partition > awareness) > >>> Java thin client does not support partition awareness. Nodejs and > python > >>> thin clients from the distribution package do not have signs of this > >>> feature as well. > >>> > >>> Igor, > >>> > >>> Could you please confirm or deny this? > >>> > >>> -Artem > >>> > >>> Artem Budnikov > >>> Technical Writergridgain.com > >>> > >>> On 03.03.2020 01:47, Denis Magda wrote: > >>> > >>> Hi Alexey, > >>> > >>> Thanks for updating the documentation. The update process is > cumbersome as > >>> of now. What will happen is that we will be replacing the content of > the > >>> current pages (pre 2.8 pages) with the content from the 2.8 versions. > Once > >>> the text is copied manually, a 2.8 version of the page will be > deleted. I > >>> would advise Artem to do that this time and update the wiki page with > more > >>> details: > >>> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document > >>> > >>> Also, why should we release this page? > >>> > https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms > >>> > >>> - > >>> Denis > >>> > >>> > >>> On Sun, Mar 1, 2020 at 7:59 AM Alexey Zinoviev > > >>> wrote: > >>> > Hi, Igniters, I've finished the ML documentation. > > I have the issue that, for example I've created a new version of page > with > postfix -2.8 and the page name contains this postfix. > How are we going to replace the URL? Or we will replace the content > from > initial page? > > For example, I've created the new version of page > > https://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees > and > moved it under new page > > https://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees-28 > How it will be processed to obtain the decision-trees url for the new > page? > > > In all case the full list of removed/replaced pages for ML is next: > > In the release 2.8, please remove the pages
Re: Ignite 2.8 documentation
Hi everyone, I have created the docs for the following items so far: * Default Ignite work dir location https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory * Baseline auto-adjust feature https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment * Cluster (de)activation events documentation https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events * Remove SqlQuery documentation done * Partition awareness for thin clients https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness * Transactions support in java thin client https://apacheignite.readme.io/docs/key-value-28#section-client-transactions * KILL QUERY command https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query * Move rebalance configuration properties to the IgniteConfiguration level https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration * Renamed IGNITE schema to SYS done I'll work on the following items today and tomorrow: * JDBC: Support for query cancellation * JDBC: Support for query timeout * suspend/resume for pessimistic transactions * WAL page compression Nikolay, How is your progress with the Metrics and System Views documentation? Artem Budnikov Technical Writer gridgain.com On 03.03.2020 19:06, Maxim Muzafarov wrote: Folks, This is in the `Ignite Core` section, so I think mostly related to java functionality and thin client protocol extension [1]. Sorry for not being too accurate with this statement . The same change is mentioned for C++ and .NET sections of the release notes (but not for other thin clients). [1] https://issues.apache.org/jira/browse/IGNITE-11898 On Tue, 3 Mar 2020 at 17:33, Igor Sapego wrote: That's right, only C++ and .NET clients have partition awareness Best Regards, Igor On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov wrote: Hi everyone, Looks like the following line from the Ignite 2.8 release notes is a bit of an overstatement and should be removed: Added support best effort affinity for thin clients (partition awareness) Java thin client does not support partition awareness. Nodejs and python thin clients from the distribution package do not have signs of this feature as well. Igor, Could you please confirm or deny this? -Artem Artem Budnikov Technical Writergridgain.com On 03.03.2020 01:47, Denis Magda wrote: Hi Alexey, Thanks for updating the documentation. The update process is cumbersome as of now. What will happen is that we will be replacing the content of the current pages (pre 2.8 pages) with the content from the 2.8 versions. Once the text is copied manually, a 2.8 version of the page will be deleted. I would advise Artem to do that this time and update the wiki page with more details: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document Also, why should we release this page? https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms - Denis On Sun, Mar 1, 2020 at 7:59 AM Alexey Zinoviev wrote: Hi, Igniters, I've finished the ML documentation. I have the issue that, for example I've created a new version of page with postfix -2.8 and the page name contains this postfix. How are we going to replace the URL? Or we will replace the content from initial page? For example, I've created the new version of page https://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees and moved it under new page https://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees-28 How it will be processed to obtain the decision-trees url for the new page? In all case the full list of removed/replaced pages for ML is next: In the release 2.8, please remove the pages 1. https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms 2. https://dash.readme.io/project/apacheignite/v2.7.6/docs/svm-multi-class-classification 3. DeepLearning block with 3 pages 4. https://dash.readme.io/project/apacheignite/v2.7.6/docs/model-cross-validation Next pages were replaced with postfix 2.8 and grouped under new pages 1. https://dash.readme.io/project/apacheignite/v2.7.6/docs/machine-learning 2. https://dash.readme.io/project/apacheignite/v2.7.6/docs/preprocessing 3. https://dash.readme.io/project/apacheignite/v2.7.6/docs/ols-multiple-linear-regression 4. https://dash.readme.io/project/apacheignite/v2.7.6/docs/k-means-clustering 5. https://dash.readme.io/project/apacheignite/v2.7.6/docs/multilayer-perceptron 6. https://dash.readme.io/project/apacheignite/v2.7.6/docs/knn-classification 7. https://dash.readme.io/project/apacheignite/v2.7.6/docs/knn-regression 8.
Re: Ignite 2.8 documentation
Hi everyone, I have created the docs for the following items so far: -Default Ignite work dir location https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory - Baseline auto-adjust feature https://apacheignite.readme.io/docs/baseline-topology-28#section-baseline-topology-autoadjustment - Cluster (de)activation events documentation https://apacheignite.readme.io/docs/baseline-topology-28#section-cluster-activationdeactivation-events - Remove SqlQuery documentation done - Partition awareness for thin clients https://apacheignite-net.readme.io/docs/thin-client-28#section-partition-awareness https://apacheignite-cpp.readme.io/docs/thin-client-28#section-partition-awareness - Transactions support in java thin client https://apacheignite.readme.io/docs/key-value-28#section-client-transactions - KILL QUERY command https://dash.readme.io/project/apacheignite-sql/v2.7.6/docs/kill-query - Move rebalance configuration properties to the IgniteConfiguration level https://apacheignite.readme.io/docs/data-rebalancing-28#section-configuration - Renamed IGNITE schema to SYS done Artem Budnikov Technical Writergridgain.com On 03.03.2020 19:06, Maxim Muzafarov wrote: Folks, This is in the `Ignite Core` section, so I think mostly related to java functionality and thin client protocol extension [1]. Sorry for not being too accurate with this statement . The same change is mentioned for C++ and .NET sections of the release notes (but not for other thin clients). [1] https://issues.apache.org/jira/browse/IGNITE-11898 On Tue, 3 Mar 2020 at 17:33, Igor Sapego wrote: That's right, only C++ and .NET clients have partition awareness Best Regards, Igor On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov wrote: Hi everyone, Looks like the following line from the Ignite 2.8 release notes is a bit of an overstatement and should be removed: Added support best effort affinity for thin clients (partition awareness) Java thin client does not support partition awareness. Nodejs and python thin clients from the distribution package do not have signs of this feature as well. Igor, Could you please confirm or deny this? -Artem Artem Budnikov Technical Writergridgain.com On 03.03.2020 01:47, Denis Magda wrote: Hi Alexey, Thanks for updating the documentation. The update process is cumbersome as of now. What will happen is that we will be replacing the content of the current pages (pre 2.8 pages) with the content from the 2.8 versions. Once the text is copied manually, a 2.8 version of the page will be deleted. I would advise Artem to do that this time and update the wiki page with more details:https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document Also, why should we release this page?https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms - Denis On Sun, Mar 1, 2020 at 7:59 AM Alexey Zinoviev wrote: Hi, Igniters, I've finished the ML documentation. I have the issue that, for example I've created a new version of page with postfix -2.8 and the page name contains this postfix. How are we going to replace the URL? Or we will replace the content from initial page? For example, I've created the new version of pagehttps://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees and moved it under new pagehttps://dash.readme.io/project/apacheignite/v2.7.6/docs/decision-trees-28 How it will be processed to obtain the decision-trees url for the new page? In all case the full list of removed/replaced pages for ML is next: In the release 2.8, please remove the pages 1. https://dash.readme.io/project/apacheignite/v2.7.6/docs/genetic-algorithms 2. https://dash.readme.io/project/apacheignite/v2.7.6/docs/svm-multi-class-classification 3. DeepLearning block with 3 pages 4. https://dash.readme.io/project/apacheignite/v2.7.6/docs/model-cross-validation Next pages were replaced with postfix 2.8 and grouped under new pages 1. https://dash.readme.io/project/apacheignite/v2.7.6/docs/machine-learning 2.https://dash.readme.io/project/apacheignite/v2.7.6/docs/preprocessing 3. https://dash.readme.io/project/apacheignite/v2.7.6/docs/ols-multiple-linear-regression 4. https://dash.readme.io/project/apacheignite/v2.7.6/docs/k-means-clustering 5. https://dash.readme.io/project/apacheignite/v2.7.6/docs/multilayer-perceptron 6. https://dash.readme.io/project/apacheignite/v2.7.6/docs/knn-classification 7.https://dash.readme.io/project/apacheignite/v2.7.6/docs/knn-regression 8. https://dash.readme.io/project/apacheignite/v2.7.6/docs/svm-binary-classification 9. https://dash.readme.io/project/apacheignite/v2.7.6/docs/logistic-regression 10.https://dash.readme.io/project/apacheignite/v2.7.6/docs/random-forest 11. https://dash.readme.io/project/apacheignite/v2.7.6/docs/gradient-boosting
Re: [RESULT] [VOTE] Release Apache Ignite 2.8.0 RC1
Docker image uploaded. > On 4 Mar 2020, at 11:37, Pavel Tupitsyn wrote: > > Maxim, what about the rest of the release steps, like Docker and NuGet? Do > you need help with that? > > On Wed, Mar 4, 2020 at 9:33 AM Alexey Zinoviev > wrote: > >> Maxim, you great, I was happy to work with you on that release, it was a >> very difficult task and it required a lot of your time, thank you >> >> ср, 4 мар. 2020 г., 8:46 Anton Vinogradov : >> >>> Awesome! >>> Thanks for leading this. >>> >>> BTW, do we have plans to start 2.9 release process in nearest future? >>> >>> On Tue, Mar 3, 2020 at 11:07 PM Maxim Muzafarov >> wrote: >>> Folks, I've done (with Santa's help) most of the steps related to the 2.8.0 RELEASE. Here are some links according to accepted the release candidate. Binary, Sources: https://dist.apache.org/repos/dist/release/ignite/2.8.0/ Bintray: https://bintray.com/apache/ignite-rpm/apache-ignite/2.8.0 https://bintray.com/apache/ignite-deb/apache-ignite/2.8.0 Javadocs: https://svn.apache.org/repos/asf/ignite/site/trunk/releases/2.8.0/ RELEASE_NOTES: >>> >> https://svn.apache.org/repos/asf/ignite/site/trunk/releases/2.8.0/release_notes.html git tag: >>> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=341b01dfd8abf2d9b01d468ad1bb26dfe84ac4f6 Download links: https://ignite.apache.org/download.cgi On Mon, 2 Mar 2020 at 22:10, Maxim Muzafarov >> wrote: > > Dear community, > > > The vote for a new release candidate is closed, now. > Vote result: The vote PASSES with 6 votes +1 (6 bindings), 0 two >> votes > and no -1. > > > +1 votes: > - Denis Magda (binding) > - Anton Vinogradov (binding) > - Pavel Tupitsyn (binding) > - Ivan Pavlukhin (binding) > - Alexey Zinoviev (binding) > - Nikolay Izhikov (binding) > > 0 votes: > - Ilya Kasnacheev (binding) > - Sergey Antonov > > > Vote thread: > >>> >> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Release-Apache-Ignite-2-8-0-RC1-td46140.html >>> >>
Re: [RESULT] [VOTE] Release Apache Ignite 2.8.0 RC1
Maxim, what about the rest of the release steps, like Docker and NuGet? Do you need help with that? On Wed, Mar 4, 2020 at 9:33 AM Alexey Zinoviev wrote: > Maxim, you great, I was happy to work with you on that release, it was a > very difficult task and it required a lot of your time, thank you > > ср, 4 мар. 2020 г., 8:46 Anton Vinogradov : > > > Awesome! > > Thanks for leading this. > > > > BTW, do we have plans to start 2.9 release process in nearest future? > > > > On Tue, Mar 3, 2020 at 11:07 PM Maxim Muzafarov > wrote: > > > > > Folks, > > > > > > > > > I've done (with Santa's help) most of the steps related to the 2.8.0 > > > RELEASE. > > > Here are some links according to accepted the release candidate. > > > > > > > > > Binary, Sources: > > > https://dist.apache.org/repos/dist/release/ignite/2.8.0/ > > > > > > Bintray: > > > https://bintray.com/apache/ignite-rpm/apache-ignite/2.8.0 > > > https://bintray.com/apache/ignite-deb/apache-ignite/2.8.0 > > > > > > Javadocs: > > > https://svn.apache.org/repos/asf/ignite/site/trunk/releases/2.8.0/ > > > > > > RELEASE_NOTES: > > > > > > > > > https://svn.apache.org/repos/asf/ignite/site/trunk/releases/2.8.0/release_notes.html > > > > > > git tag: > > > > > > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=341b01dfd8abf2d9b01d468ad1bb26dfe84ac4f6 > > > > > > Download links: > > > https://ignite.apache.org/download.cgi > > > > > > On Mon, 2 Mar 2020 at 22:10, Maxim Muzafarov > wrote: > > > > > > > > Dear community, > > > > > > > > > > > > The vote for a new release candidate is closed, now. > > > > Vote result: The vote PASSES with 6 votes +1 (6 bindings), 0 two > votes > > > > and no -1. > > > > > > > > > > > > +1 votes: > > > > - Denis Magda (binding) > > > > - Anton Vinogradov (binding) > > > > - Pavel Tupitsyn (binding) > > > > - Ivan Pavlukhin (binding) > > > > - Alexey Zinoviev (binding) > > > > - Nikolay Izhikov (binding) > > > > > > > > 0 votes: > > > > - Ilya Kasnacheev (binding) > > > > - Sergey Antonov > > > > > > > > > > > > Vote thread: > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Release-Apache-Ignite-2-8-0-RC1-td46140.html > > > > > >
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 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 wrote: > 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. > > > > 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 > > , would you be able to present the ML part? > > @Nikolay > > Izhikov or @Andrey Gura 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 > > >
Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Pavel, ++1. > 4 марта 2020 г., в 11:20, Pavel Tupitsyn написал(а): > > Igniters, > > The release has already happened. > It is on our website [1], it is on Maven [2]. > People are using it, so I don't think we can do anything at this point. > > Bugs happen, we can't delay the release forever because of them. Let's fix > things in 2.8.1. > > [1] https://ignite.apache.org/download.cgi > [2] https://mvnrepository.com/artifact/org.apache.ignite > > > On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov wrote: > >> Hello, Igniters. >> >> Do we have a person who can fix this issue in the nearest time? >> Right now IGNITE-12746 is Open and Unassigned. >> >>> 3 марта 2020 г., в 23:54, Denis Magda написал(а): >>> >>> Ilya, >>> >>> Thanks for catching that and sharing. I wonder if there are any other >>> blockers that were pushed to 2.8.x version. If there are a few then we >> can >>> produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix the >>> issue with putAll, update the binaries and finish the process. >>> >>> - >>> Denis >>> >>> >>> On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev < >> ilya.kasnach...@gmail.com> >>> wrote: >>> Hello! I have filed an issue >> https://issues.apache.org/jira/browse/IGNITE-12746 I think this is potentially a game breaker and makes me recommend >> avoiding 2.8, if we release it without fix (for now). If you are using any partitioned caches, anyway. So I suggest we withhold 2.8. Regards, -- Ilya Kasnacheev вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov : > Ilya, > > I do not want to force the release no matter what happens, but I think > we should release what we have to get feedback not just from the > developer community but from our users too. > > And fix all these issues in 2.8.1. > > On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev < >> ilya.kasnach...@gmail.com> > wrote: >> >> Hello! >> >> Can we please hold back publishing AI-2.8.0-rc1 as public Apache >> Ignite > 2.8 >> release? >> >> I have just been notified that >> > >> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated >> > >> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed >> are flaky: they seem to deadlock on putAll sorted keys maps. They used to >> pass solidly on 2.7, but fail on master and ignite-2.8. >> >> (They fail around 1 time out of 10, so just run them 25 times to >> check) >> >> If there is indeed a deadlock, this would become a blocker to this > release, >> in my opinion, but I need some time to check. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> вс, 1 мар. 2020 г. в 11:29, Maxim Muzafarov : >> >>> Ivan, >>> >>> >>> I agree with you that the more members will check the release the >>> better will be. That's why I've shared the release candidate links [1] >>> before starting a vote. The best time for starting a vote is not >>> mentioned at our release wiki page [2] (should we?) and I've also >>> failed with googling the best practices for it too. So, I've supposed >>> since all of us are working on their own tasks during weekdays the >>> free time on the weekend is the best choice for cheking\voting on the >>> release. Probably this decision was wrong. >>> >>> [1] >>> > >> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-tp43616p46117.html >>> [2] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process >>> >>> On Sun, 1 Mar 2020 at 00:37, Ivan Pavlukhin > wrote: Also I have a comment regarding to voting. Voting for 72 hour > spanning a weekend sounds a little bit odd to me. In a particular case the > more people check the release the better. And I suppose there is more time for it on weekdays for the majority. Best regards, Ivan Pavlukhin вс, 1 мар. 2020 г. в 00:33, Ivan Pavlukhin : > >> As I remember, that Pavlov suggested to discuss threats on a > private >>> PMC list > Cannot understand why it should be discussed on a private list. > What > is the clue? > > Best regards, > Ivan Pavlukhin > > сб, 29 февр. 2020 г. в 16:00, Alexey Zinoviev < > zaleslaw@gmail.com : >> >> As I remember, that Pavlov suggested to discuss threats on a > private >>> PMC >> list >> >> сб, 29 февр. 2020 г., 15:12 Ilya Kasnacheev < >>> ilya.kasnach...@gmail.com>: >>
Re: [DISCUSSION] Release Apache Ignite 2.8.0 RC1
Igniters, The release has already happened. It is on our website [1], it is on Maven [2]. People are using it, so I don't think we can do anything at this point. Bugs happen, we can't delay the release forever because of them. Let's fix things in 2.8.1. [1] https://ignite.apache.org/download.cgi [2] https://mvnrepository.com/artifact/org.apache.ignite On Wed, Mar 4, 2020 at 10:06 AM Nikolay Izhikov wrote: > Hello, Igniters. > > Do we have a person who can fix this issue in the nearest time? > Right now IGNITE-12746 is Open and Unassigned. > > > 3 марта 2020 г., в 23:54, Denis Magda написал(а): > > > > Ilya, > > > > Thanks for catching that and sharing. I wonder if there are any other > > blockers that were pushed to 2.8.x version. If there are a few then we > can > > produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix the > > issue with putAll, update the binaries and finish the process. > > > > - > > Denis > > > > > > On Tue, Mar 3, 2020 at 2:34 PM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> > > wrote: > > > >> Hello! > >> > >> I have filed an issue > https://issues.apache.org/jira/browse/IGNITE-12746 > >> > >> I think this is potentially a game breaker and makes me recommend > avoiding > >> 2.8, if we release it without fix (for now). > >> > >> If you are using any partitioned caches, anyway. > >> > >> So I suggest we withhold 2.8. > >> > >> Regards, > >> -- > >> Ilya Kasnacheev > >> > >> > >> вт, 3 мар. 2020 г. в 20:53, Maxim Muzafarov : > >> > >>> Ilya, > >>> > >>> I do not want to force the release no matter what happens, but I think > >>> we should release what we have to get feedback not just from the > >>> developer community but from our users too. > >>> > >>> And fix all these issues in 2.8.1. > >>> > >>> On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev < > ilya.kasnach...@gmail.com> > >>> wrote: > > Hello! > > Can we please hold back publishing AI-2.8.0-rc1 as public Apache > Ignite > >>> 2.8 > release? > > I have just been notified that > > >>> > >> > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated > > >>> > >> > org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed > are flaky: they seem to deadlock on putAll sorted keys maps. They used > >> to > pass solidly on 2.7, but fail on master and ignite-2.8. > > (They fail around 1 time out of 10, so just run them 25 times to > check) > > If there is indeed a deadlock, this would become a blocker to this > >>> release, > in my opinion, but I need some time to check. > > Regards, > -- > Ilya Kasnacheev > > > вс, 1 мар. 2020 г. в 11:29, Maxim Muzafarov : > > > Ivan, > > > > > > I agree with you that the more members will check the release the > > better will be. That's why I've shared the release candidate links > >> [1] > > before starting a vote. The best time for starting a vote is not > > mentioned at our release wiki page [2] (should we?) and I've also > > failed with googling the best practices for it too. So, I've supposed > > since all of us are working on their own tasks during weekdays the > > free time on the weekend is the best choice for cheking\voting on the > > release. Probably this decision was wrong. > > > > [1] > > > >>> > >> > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-tp43616p46117.html > > [2] > >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > > > On Sun, 1 Mar 2020 at 00:37, Ivan Pavlukhin > >>> wrote: > >> > >> Also I have a comment regarding to voting. Voting for 72 hour > >>> spanning > >> a weekend sounds a little bit odd to me. In a particular case the > >>> more > >> people check the release the better. And I suppose there is more > >> time > >> for it on weekdays for the majority. > >> > >> Best regards, > >> Ivan Pavlukhin > >> > >> вс, 1 мар. 2020 г. в 00:33, Ivan Pavlukhin : > >>> > As I remember, that Pavlov suggested to discuss threats on a > >>> private > > PMC list > >>> Cannot understand why it should be discussed on a private list. > >>> What > >>> is the clue? > >>> > >>> Best regards, > >>> Ivan Pavlukhin > >>> > >>> сб, 29 февр. 2020 г. в 16:00, Alexey Zinoviev < > >>> zaleslaw@gmail.com > >> : > > As I remember, that Pavlov suggested to discuss threats on a > >>> private > > PMC > list > > сб, 29 февр. 2020 г., 15:12 Ilya Kasnacheev < > > ilya.kasnach...@gmail.com>: > > > Hello! > > > > As far as my understanding goes, ignite-zookeeper is listed > >> for > > removal > > because it brings a lot of
