Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, The branch ignite-2.11 [1] is ready to be released. I've prepared benchmarks (2.10 vs 2.11) [2]. It seems to me that everything is ok. I'll prepare the RC shortly. [1] https://github.com/apache/ignite/tree/ignite-2.11 [2] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11#ApacheIgnite2.11-Benchmarks[PRIMARY_SYNC,LOG_ONLY] On Thu, 9 Sept 2021 at 21:27, Denis Magda wrote: > > Maxim, > > I'm good with your plan. Thanks for sharing the details. Let's follow the > plan and release 2.11 asap. > > - > Denis > > On Thu, Sep 9, 2021 at 1:02 PM Maxim Muzafarov wrote: > > > Folks, Denis, > > > > > > I disagree with you that the changes are ready. They are not compiling > > and require additional manual tests. I see the following reasons: > > - The major version of dependencies are changed; > > - Handling of error codes output changed; > > - For a new module developed in 2021 the old version of dependency was > > used 12.0.0 (Oct, 2019) instead of the new one available 12.11.0 (Apr, > > 2021). I don't think this was done unintentionally and additional > > investigation is required. > > - The patch [1] to fix the build is ready more than 1 week ago and we > > still don't have a maintainer for it who will lead this change. > > > > I'd like to mention also that the master branch build and the release > > branch build are still BROKEN. > > > > > > Denis, > > > > I'd like to unblock the 2.11 release pipeline and continue with > > preparing the RC taking into account the azure integration is also > > important for Apache Ignite users. The other changes are also waiting > > to be released for a long time. > > > > So, here is my plan: > > - I'll rollback the changes [1] from the release branch. > > - I'll merge [1] to the master branch to fix the build. > > - Currently, I've limited free time, but I'll try to check the changes > > [1] in the real azure environment by myself (probably at the end of > > October). > > - I'll write a letter with your support on behalf of PMCs to the > > Microsoft Azure support and do my best to find some free > > resources/credits for our open-source CI project. > > - I'll initiate a discussion about moving the AWZ, GCE, Azure modules > > to the ignite-extensions project and I hope the community will support > > this activity (after all release modules under extensions if need). > > - Depending on the discussion with the Azure team, the TC > > configuration is needed, so I think your help or the help of someone > > from the community will be required here (to run at least basic > > suites). > > > > WDYT? > > Can we proceed with the release? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > On Tue, 7 Sept 2021 at 18:59, Denis Magda wrote: > > > > > > Maxim, > > > > > > I've found an original ticket where Ilya was helping with review and > > > testing of the Azure IP finder: > > > https://issues.apache.org/jira/browse/IGNITE-14346 > > > As I understand, the ticket you're referring to bumps up the version and > > > introduces some other little changes: > > > https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > @Vladimir Pligin , could you please help with the > > > test in a real Azure environment? See IGNITE-15388 > > > > > > - > > > Denis > > > > > > On Tue, Sep 7, 2021 at 10:46 AM Denis Magda wrote: > > > > > > > Maxim, > > > > > > > > I don't think we're rushing to release the changes. It seems to me that > > > > the integration is ready and can be released to the app developers. If > > we > > > > put it off until the next release to add an automated test in the real > > > > environment, it can take an unpredictable amount of time before it gets > > > > released (someone needs to contribute the test and figure the Azure > > > > sponsorship matter). > > > > > > > > Atri, can you please deploy a 2-node cluster in Azure on separate > > virtual > > > > machines to validate that the IP finder works in this configuration? > > This > > > > is a typical usage scenario for the IP finder - multiple node instances > > > > span multiple VMs. If this works, then I would release the > > contribution. > > > > > > > > - > > > > Denis > > > > > > > > On Tue, Sep 7, 2021 at 10:01 AM Maxim Muzafarov > > wrote: > > > > > > > >> Denis, > > > >> > > > >> AWS has a promotional credits program for open-source projects [1], > > > >> maybe Azure has something similar too. Have we checked this topic at > > > >> least? > > > >> I'm not against the changes themselves, they are important for sure. > > > >> However, for me, such changes are not as simple as they seem at first > > > >> glance and require some time-consumption additional resources and > > > >> configurations. I'm glad to provide any help for releasing these > > > >> changes but I don't understand why we are rushing with them. And > > > >> please don't take words too harshly maybe I just missing some details. > > > >> > > > >> > > > >> [1] > > > >> > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Maxim, I'm good with your plan. Thanks for sharing the details. Let's follow the plan and release 2.11 asap. - Denis On Thu, Sep 9, 2021 at 1:02 PM Maxim Muzafarov wrote: > Folks, Denis, > > > I disagree with you that the changes are ready. They are not compiling > and require additional manual tests. I see the following reasons: > - The major version of dependencies are changed; > - Handling of error codes output changed; > - For a new module developed in 2021 the old version of dependency was > used 12.0.0 (Oct, 2019) instead of the new one available 12.11.0 (Apr, > 2021). I don't think this was done unintentionally and additional > investigation is required. > - The patch [1] to fix the build is ready more than 1 week ago and we > still don't have a maintainer for it who will lead this change. > > I'd like to mention also that the master branch build and the release > branch build are still BROKEN. > > > Denis, > > I'd like to unblock the 2.11 release pipeline and continue with > preparing the RC taking into account the azure integration is also > important for Apache Ignite users. The other changes are also waiting > to be released for a long time. > > So, here is my plan: > - I'll rollback the changes [1] from the release branch. > - I'll merge [1] to the master branch to fix the build. > - Currently, I've limited free time, but I'll try to check the changes > [1] in the real azure environment by myself (probably at the end of > October). > - I'll write a letter with your support on behalf of PMCs to the > Microsoft Azure support and do my best to find some free > resources/credits for our open-source CI project. > - I'll initiate a discussion about moving the AWZ, GCE, Azure modules > to the ignite-extensions project and I hope the community will support > this activity (after all release modules under extensions if need). > - Depending on the discussion with the Azure team, the TC > configuration is needed, so I think your help or the help of someone > from the community will be required here (to run at least basic > suites). > > WDYT? > Can we proceed with the release? > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > On Tue, 7 Sept 2021 at 18:59, Denis Magda wrote: > > > > Maxim, > > > > I've found an original ticket where Ilya was helping with review and > > testing of the Azure IP finder: > > https://issues.apache.org/jira/browse/IGNITE-14346 > > As I understand, the ticket you're referring to bumps up the version and > > introduces some other little changes: > > https://issues.apache.org/jira/browse/IGNITE-15388 > > > > @Vladimir Pligin , could you please help with the > > test in a real Azure environment? See IGNITE-15388 > > > > - > > Denis > > > > On Tue, Sep 7, 2021 at 10:46 AM Denis Magda wrote: > > > > > Maxim, > > > > > > I don't think we're rushing to release the changes. It seems to me that > > > the integration is ready and can be released to the app developers. If > we > > > put it off until the next release to add an automated test in the real > > > environment, it can take an unpredictable amount of time before it gets > > > released (someone needs to contribute the test and figure the Azure > > > sponsorship matter). > > > > > > Atri, can you please deploy a 2-node cluster in Azure on separate > virtual > > > machines to validate that the IP finder works in this configuration? > This > > > is a typical usage scenario for the IP finder - multiple node instances > > > span multiple VMs. If this works, then I would release the > contribution. > > > > > > - > > > Denis > > > > > > On Tue, Sep 7, 2021 at 10:01 AM Maxim Muzafarov > wrote: > > > > > >> Denis, > > >> > > >> AWS has a promotional credits program for open-source projects [1], > > >> maybe Azure has something similar too. Have we checked this topic at > > >> least? > > >> I'm not against the changes themselves, they are important for sure. > > >> However, for me, such changes are not as simple as they seem at first > > >> glance and require some time-consumption additional resources and > > >> configurations. I'm glad to provide any help for releasing these > > >> changes but I don't understand why we are rushing with them. And > > >> please don't take words too harshly maybe I just missing some details. > > >> > > >> > > >> [1] > > >> > https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/ > > >> > > >> On Tue, 7 Sept 2021 at 16:20, Denis Magda wrote: > > >> > > > >> > Maxim, > > >> > > > >> > What's is the "standard way" and who is going to implement this > standard > > >> > approach for the Azure module? Just curious about the ETA of this > > >> feature > > >> > availability. Ignite developers have been requesting the capability > for > > >> a > > >> > while and here it is. We're blocking it because of a missing > automated > > >> test > > >> > for a real environment. Who is going to develop those tests and, > more > > >> > importantly, sponsor Azure resources? > > >>
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, Denis, I disagree with you that the changes are ready. They are not compiling and require additional manual tests. I see the following reasons: - The major version of dependencies are changed; - Handling of error codes output changed; - For a new module developed in 2021 the old version of dependency was used 12.0.0 (Oct, 2019) instead of the new one available 12.11.0 (Apr, 2021). I don't think this was done unintentionally and additional investigation is required. - The patch [1] to fix the build is ready more than 1 week ago and we still don't have a maintainer for it who will lead this change. I'd like to mention also that the master branch build and the release branch build are still BROKEN. Denis, I'd like to unblock the 2.11 release pipeline and continue with preparing the RC taking into account the azure integration is also important for Apache Ignite users. The other changes are also waiting to be released for a long time. So, here is my plan: - I'll rollback the changes [1] from the release branch. - I'll merge [1] to the master branch to fix the build. - Currently, I've limited free time, but I'll try to check the changes [1] in the real azure environment by myself (probably at the end of October). - I'll write a letter with your support on behalf of PMCs to the Microsoft Azure support and do my best to find some free resources/credits for our open-source CI project. - I'll initiate a discussion about moving the AWZ, GCE, Azure modules to the ignite-extensions project and I hope the community will support this activity (after all release modules under extensions if need). - Depending on the discussion with the Azure team, the TC configuration is needed, so I think your help or the help of someone from the community will be required here (to run at least basic suites). WDYT? Can we proceed with the release? [1] https://issues.apache.org/jira/browse/IGNITE-15388 On Tue, 7 Sept 2021 at 18:59, Denis Magda wrote: > > Maxim, > > I've found an original ticket where Ilya was helping with review and > testing of the Azure IP finder: > https://issues.apache.org/jira/browse/IGNITE-14346 > As I understand, the ticket you're referring to bumps up the version and > introduces some other little changes: > https://issues.apache.org/jira/browse/IGNITE-15388 > > @Vladimir Pligin , could you please help with the > test in a real Azure environment? See IGNITE-15388 > > - > Denis > > On Tue, Sep 7, 2021 at 10:46 AM Denis Magda wrote: > > > Maxim, > > > > I don't think we're rushing to release the changes. It seems to me that > > the integration is ready and can be released to the app developers. If we > > put it off until the next release to add an automated test in the real > > environment, it can take an unpredictable amount of time before it gets > > released (someone needs to contribute the test and figure the Azure > > sponsorship matter). > > > > Atri, can you please deploy a 2-node cluster in Azure on separate virtual > > machines to validate that the IP finder works in this configuration? This > > is a typical usage scenario for the IP finder - multiple node instances > > span multiple VMs. If this works, then I would release the contribution. > > > > - > > Denis > > > > On Tue, Sep 7, 2021 at 10:01 AM Maxim Muzafarov wrote: > > > >> Denis, > >> > >> AWS has a promotional credits program for open-source projects [1], > >> maybe Azure has something similar too. Have we checked this topic at > >> least? > >> I'm not against the changes themselves, they are important for sure. > >> However, for me, such changes are not as simple as they seem at first > >> glance and require some time-consumption additional resources and > >> configurations. I'm glad to provide any help for releasing these > >> changes but I don't understand why we are rushing with them. And > >> please don't take words too harshly maybe I just missing some details. > >> > >> > >> [1] > >> https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/ > >> > >> On Tue, 7 Sept 2021 at 16:20, Denis Magda wrote: > >> > > >> > Maxim, > >> > > >> > What's is the "standard way" and who is going to implement this standard > >> > approach for the Azure module? Just curious about the ETA of this > >> feature > >> > availability. Ignite developers have been requesting the capability for > >> a > >> > while and here it is. We're blocking it because of a missing automated > >> test > >> > for a real environment. Who is going to develop those tests and, more > >> > importantly, sponsor Azure resources? > >> > > >> > - > >> > Denis > >> > > >> > On Tue, Sep 7, 2021 at 8:03 AM Maxim Muzafarov > >> wrote: > >> > > >> > > Denis, > >> > > > >> > > Thank you for sharing the details. They look great! > >> > > > >> > > Can you clarify what is the reason for rushing these changes? Why we > >> > > should merge changes without test coverage in the 2.11 release without > >> > > doing it a standard way? Please, don't say that
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Maxim, I've found an original ticket where Ilya was helping with review and testing of the Azure IP finder: https://issues.apache.org/jira/browse/IGNITE-14346 As I understand, the ticket you're referring to bumps up the version and introduces some other little changes: https://issues.apache.org/jira/browse/IGNITE-15388 @Vladimir Pligin , could you please help with the test in a real Azure environment? See IGNITE-15388 - Denis On Tue, Sep 7, 2021 at 10:46 AM Denis Magda wrote: > Maxim, > > I don't think we're rushing to release the changes. It seems to me that > the integration is ready and can be released to the app developers. If we > put it off until the next release to add an automated test in the real > environment, it can take an unpredictable amount of time before it gets > released (someone needs to contribute the test and figure the Azure > sponsorship matter). > > Atri, can you please deploy a 2-node cluster in Azure on separate virtual > machines to validate that the IP finder works in this configuration? This > is a typical usage scenario for the IP finder - multiple node instances > span multiple VMs. If this works, then I would release the contribution. > > - > Denis > > On Tue, Sep 7, 2021 at 10:01 AM Maxim Muzafarov wrote: > >> Denis, >> >> AWS has a promotional credits program for open-source projects [1], >> maybe Azure has something similar too. Have we checked this topic at >> least? >> I'm not against the changes themselves, they are important for sure. >> However, for me, such changes are not as simple as they seem at first >> glance and require some time-consumption additional resources and >> configurations. I'm glad to provide any help for releasing these >> changes but I don't understand why we are rushing with them. And >> please don't take words too harshly maybe I just missing some details. >> >> >> [1] >> https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/ >> >> On Tue, 7 Sept 2021 at 16:20, Denis Magda wrote: >> > >> > Maxim, >> > >> > What's is the "standard way" and who is going to implement this standard >> > approach for the Azure module? Just curious about the ETA of this >> feature >> > availability. Ignite developers have been requesting the capability for >> a >> > while and here it is. We're blocking it because of a missing automated >> test >> > for a real environment. Who is going to develop those tests and, more >> > importantly, sponsor Azure resources? >> > >> > - >> > Denis >> > >> > On Tue, Sep 7, 2021 at 8:03 AM Maxim Muzafarov >> wrote: >> > >> > > Denis, >> > > >> > > Thank you for sharing the details. They look great! >> > > >> > > Can you clarify what is the reason for rushing these changes? Why we >> > > should merge changes without test coverage in the 2.11 release without >> > > doing it a standard way? Please, don't say that we always do such >> > > things for other modules, it breaks my heart :-) >> > > >> > > On Tue, 7 Sept 2021 at 14:58, Pavel Pereslegin >> wrote: >> > > > >> > > > Denis, >> > > > >> > > > if Atri looked at the changes why didn't he left any comments or >> > > > review approval? >> > > > >> > > > Only the ipfinder test was checked in Azure, it is essentially >> > > > synthetic, is it enough? As far as I understand, we have to deploy >> > > > Ignite itself in the cloud and play with it to make sure it works, >> > > > unfortunately, I do not have the competence, as well as free time to >> > > > study how to do this, so we asked for help. >> > > > >> > > > вт, 7 сент. 2021 г. в 14:23, Denis Magda : >> > > > > >> > > > > Maxim, >> > > > > >> > > > > Regardless of a lack of automated testing in a real environment, >> our >> > > AWS, >> > > > > GCE and other modules are used actively by the users and we don't >> > > receive >> > > > > issue reports. Here are the numbers: >> > > > > >> > > > >- AWS - 7000 *monthly* Maven downloads on average >> > > > >- GCE - 350 downloads >> > > > >- Kubernetes - 6000 downloads >> > > > > >> > > > > So they are far from dead. >> > > > > >> > > > > I think it's not corrected to skip the Azure integration from the >> > > release >> > > > > only because it follows the same testing approach. If you propose >> to >> > > change >> > > > > it, then let's do it outside of this discussion and for all the >> > > modules. >> > > > > The first step would be to find a sponsor who is ready to >> provision >> > > > > resources on the cloud environments (that was the main obstacle >> when >> > > the >> > > > > current test suites were being created). >> > > > > >> > > > > I don't know, currently, I'm not able to verify the results of >> this >> > > > > > execution. >> > > > > >> > > > > >> > > > > The module was verified by Atri and Pavel. This looks enough. If >> you >> > > have >> > > > > doubts, you can also double-check the code and work with Atri in >> case >> > > any >> > > > > issue arises. >> > > > > >> > > > > -- >> > > > > Denis >> > > > > >> > > > > - >>
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Maxim, I don't think we're rushing to release the changes. It seems to me that the integration is ready and can be released to the app developers. If we put it off until the next release to add an automated test in the real environment, it can take an unpredictable amount of time before it gets released (someone needs to contribute the test and figure the Azure sponsorship matter). Atri, can you please deploy a 2-node cluster in Azure on separate virtual machines to validate that the IP finder works in this configuration? This is a typical usage scenario for the IP finder - multiple node instances span multiple VMs. If this works, then I would release the contribution. - Denis On Tue, Sep 7, 2021 at 10:01 AM Maxim Muzafarov wrote: > Denis, > > AWS has a promotional credits program for open-source projects [1], > maybe Azure has something similar too. Have we checked this topic at > least? > I'm not against the changes themselves, they are important for sure. > However, for me, such changes are not as simple as they seem at first > glance and require some time-consumption additional resources and > configurations. I'm glad to provide any help for releasing these > changes but I don't understand why we are rushing with them. And > please don't take words too harshly maybe I just missing some details. > > > [1] > https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/ > > On Tue, 7 Sept 2021 at 16:20, Denis Magda wrote: > > > > Maxim, > > > > What's is the "standard way" and who is going to implement this standard > > approach for the Azure module? Just curious about the ETA of this feature > > availability. Ignite developers have been requesting the capability for a > > while and here it is. We're blocking it because of a missing automated > test > > for a real environment. Who is going to develop those tests and, more > > importantly, sponsor Azure resources? > > > > - > > Denis > > > > On Tue, Sep 7, 2021 at 8:03 AM Maxim Muzafarov > wrote: > > > > > Denis, > > > > > > Thank you for sharing the details. They look great! > > > > > > Can you clarify what is the reason for rushing these changes? Why we > > > should merge changes without test coverage in the 2.11 release without > > > doing it a standard way? Please, don't say that we always do such > > > things for other modules, it breaks my heart :-) > > > > > > On Tue, 7 Sept 2021 at 14:58, Pavel Pereslegin > wrote: > > > > > > > > Denis, > > > > > > > > if Atri looked at the changes why didn't he left any comments or > > > > review approval? > > > > > > > > Only the ipfinder test was checked in Azure, it is essentially > > > > synthetic, is it enough? As far as I understand, we have to deploy > > > > Ignite itself in the cloud and play with it to make sure it works, > > > > unfortunately, I do not have the competence, as well as free time to > > > > study how to do this, so we asked for help. > > > > > > > > вт, 7 сент. 2021 г. в 14:23, Denis Magda : > > > > > > > > > > Maxim, > > > > > > > > > > Regardless of a lack of automated testing in a real environment, > our > > > AWS, > > > > > GCE and other modules are used actively by the users and we don't > > > receive > > > > > issue reports. Here are the numbers: > > > > > > > > > >- AWS - 7000 *monthly* Maven downloads on average > > > > >- GCE - 350 downloads > > > > >- Kubernetes - 6000 downloads > > > > > > > > > > So they are far from dead. > > > > > > > > > > I think it's not corrected to skip the Azure integration from the > > > release > > > > > only because it follows the same testing approach. If you propose > to > > > change > > > > > it, then let's do it outside of this discussion and for all the > > > modules. > > > > > The first step would be to find a sponsor who is ready to provision > > > > > resources on the cloud environments (that was the main obstacle > when > > > the > > > > > current test suites were being created). > > > > > > > > > > I don't know, currently, I'm not able to verify the results of this > > > > > > execution. > > > > > > > > > > > > > > > The module was verified by Atri and Pavel. This looks enough. If > you > > > have > > > > > doubts, you can also double-check the code and work with Atri in > case > > > any > > > > > issue arises. > > > > > > > > > > -- > > > > > Denis > > > > > > > > > > - > > > > > Denis > > > > > > > > > > On Mon, Sep 6, 2021 at 2:50 PM Maxim Muzafarov > > > wrote: > > > > > > > > > > > Atri, > > > > > > > > > > > > I don't know, currently, I'm not able to verify the results of > this > > > > > > execution. For instance, we have the > TcpDiscoveryZookeeperIpFinder > > > and > > > > > > it has the corresponding test suite on the TeamCity server, so > when I > > > > > > make code changes I can verify these changes on the test > environment. > > > > > > How can we be sure that new changes in TCP discovery Ignite's > > > > > > component won't break the Azure module? I don't think we should > allow >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Denis, AWS has a promotional credits program for open-source projects [1], maybe Azure has something similar too. Have we checked this topic at least? I'm not against the changes themselves, they are important for sure. However, for me, such changes are not as simple as they seem at first glance and require some time-consumption additional resources and configurations. I'm glad to provide any help for releasing these changes but I don't understand why we are rushing with them. And please don't take words too harshly maybe I just missing some details. [1] https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/ On Tue, 7 Sept 2021 at 16:20, Denis Magda wrote: > > Maxim, > > What's is the "standard way" and who is going to implement this standard > approach for the Azure module? Just curious about the ETA of this feature > availability. Ignite developers have been requesting the capability for a > while and here it is. We're blocking it because of a missing automated test > for a real environment. Who is going to develop those tests and, more > importantly, sponsor Azure resources? > > - > Denis > > On Tue, Sep 7, 2021 at 8:03 AM Maxim Muzafarov wrote: > > > Denis, > > > > Thank you for sharing the details. They look great! > > > > Can you clarify what is the reason for rushing these changes? Why we > > should merge changes without test coverage in the 2.11 release without > > doing it a standard way? Please, don't say that we always do such > > things for other modules, it breaks my heart :-) > > > > On Tue, 7 Sept 2021 at 14:58, Pavel Pereslegin wrote: > > > > > > Denis, > > > > > > if Atri looked at the changes why didn't he left any comments or > > > review approval? > > > > > > Only the ipfinder test was checked in Azure, it is essentially > > > synthetic, is it enough? As far as I understand, we have to deploy > > > Ignite itself in the cloud and play with it to make sure it works, > > > unfortunately, I do not have the competence, as well as free time to > > > study how to do this, so we asked for help. > > > > > > вт, 7 сент. 2021 г. в 14:23, Denis Magda : > > > > > > > > Maxim, > > > > > > > > Regardless of a lack of automated testing in a real environment, our > > AWS, > > > > GCE and other modules are used actively by the users and we don't > > receive > > > > issue reports. Here are the numbers: > > > > > > > >- AWS - 7000 *monthly* Maven downloads on average > > > >- GCE - 350 downloads > > > >- Kubernetes - 6000 downloads > > > > > > > > So they are far from dead. > > > > > > > > I think it's not corrected to skip the Azure integration from the > > release > > > > only because it follows the same testing approach. If you propose to > > change > > > > it, then let's do it outside of this discussion and for all the > > modules. > > > > The first step would be to find a sponsor who is ready to provision > > > > resources on the cloud environments (that was the main obstacle when > > the > > > > current test suites were being created). > > > > > > > > I don't know, currently, I'm not able to verify the results of this > > > > > execution. > > > > > > > > > > > > The module was verified by Atri and Pavel. This looks enough. If you > > have > > > > doubts, you can also double-check the code and work with Atri in case > > any > > > > issue arises. > > > > > > > > -- > > > > Denis > > > > > > > > - > > > > Denis > > > > > > > > On Mon, Sep 6, 2021 at 2:50 PM Maxim Muzafarov > > wrote: > > > > > > > > > Atri, > > > > > > > > > > I don't know, currently, I'm not able to verify the results of this > > > > > execution. For instance, we have the TcpDiscoveryZookeeperIpFinder > > and > > > > > it has the corresponding test suite on the TeamCity server, so when I > > > > > make code changes I can verify these changes on the test environment. > > > > > How can we be sure that new changes in TCP discovery Ignite's > > > > > component won't break the Azure module? I don't think we should allow > > > > > such a practice at all, so the AWS and GCE is not a good example > > here. > > > > > Probably we don't know are they work correctly at all because they > > are > > > > > don't even used by users. > > > > > > > > > > On Mon, 6 Sept 2021 at 21:18, Atri Sharma wrote: > > > > > > > > > > > > Maxim, > > > > > > > > > > > > I thought Pavel has already reported that the tests run fine with a > > > > > > valid Azure account? > > > > > > > > > > > > On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov > > > > > > > wrote: > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > Sorry for the reminder :-) > > > > > > > > > > > > > > This issue [1] still blocks the release and the development. > > There is > > > > > > > a week that has passed, however, the issue is still not resolved > > and > > > > > > > cannot be validated within a reasonable time frame. Trust is a > > good > > > > > > > thing and all the community members should trust each other, but > > we > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Maxim, What's is the "standard way" and who is going to implement this standard approach for the Azure module? Just curious about the ETA of this feature availability. Ignite developers have been requesting the capability for a while and here it is. We're blocking it because of a missing automated test for a real environment. Who is going to develop those tests and, more importantly, sponsor Azure resources? - Denis On Tue, Sep 7, 2021 at 8:03 AM Maxim Muzafarov wrote: > Denis, > > Thank you for sharing the details. They look great! > > Can you clarify what is the reason for rushing these changes? Why we > should merge changes without test coverage in the 2.11 release without > doing it a standard way? Please, don't say that we always do such > things for other modules, it breaks my heart :-) > > On Tue, 7 Sept 2021 at 14:58, Pavel Pereslegin wrote: > > > > Denis, > > > > if Atri looked at the changes why didn't he left any comments or > > review approval? > > > > Only the ipfinder test was checked in Azure, it is essentially > > synthetic, is it enough? As far as I understand, we have to deploy > > Ignite itself in the cloud and play with it to make sure it works, > > unfortunately, I do not have the competence, as well as free time to > > study how to do this, so we asked for help. > > > > вт, 7 сент. 2021 г. в 14:23, Denis Magda : > > > > > > Maxim, > > > > > > Regardless of a lack of automated testing in a real environment, our > AWS, > > > GCE and other modules are used actively by the users and we don't > receive > > > issue reports. Here are the numbers: > > > > > >- AWS - 7000 *monthly* Maven downloads on average > > >- GCE - 350 downloads > > >- Kubernetes - 6000 downloads > > > > > > So they are far from dead. > > > > > > I think it's not corrected to skip the Azure integration from the > release > > > only because it follows the same testing approach. If you propose to > change > > > it, then let's do it outside of this discussion and for all the > modules. > > > The first step would be to find a sponsor who is ready to provision > > > resources on the cloud environments (that was the main obstacle when > the > > > current test suites were being created). > > > > > > I don't know, currently, I'm not able to verify the results of this > > > > execution. > > > > > > > > > The module was verified by Atri and Pavel. This looks enough. If you > have > > > doubts, you can also double-check the code and work with Atri in case > any > > > issue arises. > > > > > > -- > > > Denis > > > > > > - > > > Denis > > > > > > On Mon, Sep 6, 2021 at 2:50 PM Maxim Muzafarov > wrote: > > > > > > > Atri, > > > > > > > > I don't know, currently, I'm not able to verify the results of this > > > > execution. For instance, we have the TcpDiscoveryZookeeperIpFinder > and > > > > it has the corresponding test suite on the TeamCity server, so when I > > > > make code changes I can verify these changes on the test environment. > > > > How can we be sure that new changes in TCP discovery Ignite's > > > > component won't break the Azure module? I don't think we should allow > > > > such a practice at all, so the AWS and GCE is not a good example > here. > > > > Probably we don't know are they work correctly at all because they > are > > > > don't even used by users. > > > > > > > > On Mon, 6 Sept 2021 at 21:18, Atri Sharma wrote: > > > > > > > > > > Maxim, > > > > > > > > > > I thought Pavel has already reported that the tests run fine with a > > > > > valid Azure account? > > > > > > > > > > On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov > > > > > wrote: > > > > > > > > > > > > Folks, > > > > > > > > > > > > Sorry for the reminder :-) > > > > > > > > > > > > This issue [1] still blocks the release and the development. > There is > > > > > > a week that has passed, however, the issue is still not resolved > and > > > > > > cannot be validated within a reasonable time frame. Trust is a > good > > > > > > thing and all the community members should trust each other, but > we > > > > > > still have the RTC procedure and I don't think we should refuse > оf it > > > > > > just because of trust and all of us are highly qualified > engineers. > > > > > > This is my humble opinion, but I don't think that this issue [1] > is a > > > > > > good candidate to include the release since additional checks are > > > > > > still required. Things like this can quickly turn into dead code > (like > > > > > > the AWS and GCE modules do) and it's better to add additional > tests > > > > > > for it prior to release them. > > > > > > > > > > > > So here is the plan: > > > > > > > > > > > > - revert [1] from the release 2.11 branch (I'll do it tomorrow) > > > > > > - commit the [1] to the master branch (success build is enough > > > > > > verification for this at this moment) > > > > > > - create and configure TC with a technical azure account to test > such > > > > module > > > > > > - initiate a discussion to move Azure, AWS,
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Denis, Thank you for sharing the details. They look great! Can you clarify what is the reason for rushing these changes? Why we should merge changes without test coverage in the 2.11 release without doing it a standard way? Please, don't say that we always do such things for other modules, it breaks my heart :-) On Tue, 7 Sept 2021 at 14:58, Pavel Pereslegin wrote: > > Denis, > > if Atri looked at the changes why didn't he left any comments or > review approval? > > Only the ipfinder test was checked in Azure, it is essentially > synthetic, is it enough? As far as I understand, we have to deploy > Ignite itself in the cloud and play with it to make sure it works, > unfortunately, I do not have the competence, as well as free time to > study how to do this, so we asked for help. > > вт, 7 сент. 2021 г. в 14:23, Denis Magda : > > > > Maxim, > > > > Regardless of a lack of automated testing in a real environment, our AWS, > > GCE and other modules are used actively by the users and we don't receive > > issue reports. Here are the numbers: > > > >- AWS - 7000 *monthly* Maven downloads on average > >- GCE - 350 downloads > >- Kubernetes - 6000 downloads > > > > So they are far from dead. > > > > I think it's not corrected to skip the Azure integration from the release > > only because it follows the same testing approach. If you propose to change > > it, then let's do it outside of this discussion and for all the modules. > > The first step would be to find a sponsor who is ready to provision > > resources on the cloud environments (that was the main obstacle when the > > current test suites were being created). > > > > I don't know, currently, I'm not able to verify the results of this > > > execution. > > > > > > The module was verified by Atri and Pavel. This looks enough. If you have > > doubts, you can also double-check the code and work with Atri in case any > > issue arises. > > > > -- > > Denis > > > > - > > Denis > > > > On Mon, Sep 6, 2021 at 2:50 PM Maxim Muzafarov wrote: > > > > > Atri, > > > > > > I don't know, currently, I'm not able to verify the results of this > > > execution. For instance, we have the TcpDiscoveryZookeeperIpFinder and > > > it has the corresponding test suite on the TeamCity server, so when I > > > make code changes I can verify these changes on the test environment. > > > How can we be sure that new changes in TCP discovery Ignite's > > > component won't break the Azure module? I don't think we should allow > > > such a practice at all, so the AWS and GCE is not a good example here. > > > Probably we don't know are they work correctly at all because they are > > > don't even used by users. > > > > > > On Mon, 6 Sept 2021 at 21:18, Atri Sharma wrote: > > > > > > > > Maxim, > > > > > > > > I thought Pavel has already reported that the tests run fine with a > > > > valid Azure account? > > > > > > > > On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov > > > wrote: > > > > > > > > > > Folks, > > > > > > > > > > Sorry for the reminder :-) > > > > > > > > > > This issue [1] still blocks the release and the development. There is > > > > > a week that has passed, however, the issue is still not resolved and > > > > > cannot be validated within a reasonable time frame. Trust is a good > > > > > thing and all the community members should trust each other, but we > > > > > still have the RTC procedure and I don't think we should refuse оf it > > > > > just because of trust and all of us are highly qualified engineers. > > > > > This is my humble opinion, but I don't think that this issue [1] is a > > > > > good candidate to include the release since additional checks are > > > > > still required. Things like this can quickly turn into dead code (like > > > > > the AWS and GCE modules do) and it's better to add additional tests > > > > > for it prior to release them. > > > > > > > > > > So here is the plan: > > > > > > > > > > - revert [1] from the release 2.11 branch (I'll do it tomorrow) > > > > > - commit the [1] to the master branch (success build is enough > > > > > verification for this at this moment) > > > > > - create and configure TC with a technical azure account to test such > > > module > > > > > - initiate a discussion to move Azure, AWS, GCE modules to the > > > > > ignite-extension project > > > > > - do everything above prior to the 2.12 release. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > > > > > > > > > > > On Fri, 3 Sept 2021 at 18:36, Pavel Pereslegin > > > wrote: > > > > > > > > > > > > Atri, > > > > > > > > > > > > > Anyone with azure account should be able to test it > > > > > > > > > > > > I checked the test included in the module with an Azure account (as > > > > > > I > > > > > > mentioned in Jira), it passes successfully. But I'm not sure if this > > > > > > is enough. > > > > > > > > > > > > пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov : > > > > > > > > > > > > > > Atri. > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
A cloud deployment is not needed -- you only need to set the IPFinder to Azure and deploy a local Ignite cluster. If it boots up correctly, it works fine. I did not respond because my time is severely limited these days -- please note that my employment does not incorporate contributions to Ignite. Atri On Tue, Sep 7, 2021 at 5:28 PM Pavel Pereslegin wrote: > > Denis, > > if Atri looked at the changes why didn't he left any comments or > review approval? > > Only the ipfinder test was checked in Azure, it is essentially > synthetic, is it enough? As far as I understand, we have to deploy > Ignite itself in the cloud and play with it to make sure it works, > unfortunately, I do not have the competence, as well as free time to > study how to do this, so we asked for help. > > вт, 7 сент. 2021 г. в 14:23, Denis Magda : > > > > Maxim, > > > > Regardless of a lack of automated testing in a real environment, our AWS, > > GCE and other modules are used actively by the users and we don't receive > > issue reports. Here are the numbers: > > > >- AWS - 7000 *monthly* Maven downloads on average > >- GCE - 350 downloads > >- Kubernetes - 6000 downloads > > > > So they are far from dead. > > > > I think it's not corrected to skip the Azure integration from the release > > only because it follows the same testing approach. If you propose to change > > it, then let's do it outside of this discussion and for all the modules. > > The first step would be to find a sponsor who is ready to provision > > resources on the cloud environments (that was the main obstacle when the > > current test suites were being created). > > > > I don't know, currently, I'm not able to verify the results of this > > > execution. > > > > > > The module was verified by Atri and Pavel. This looks enough. If you have > > doubts, you can also double-check the code and work with Atri in case any > > issue arises. > > > > -- > > Denis > > > > - > > Denis > > > > On Mon, Sep 6, 2021 at 2:50 PM Maxim Muzafarov wrote: > > > > > Atri, > > > > > > I don't know, currently, I'm not able to verify the results of this > > > execution. For instance, we have the TcpDiscoveryZookeeperIpFinder and > > > it has the corresponding test suite on the TeamCity server, so when I > > > make code changes I can verify these changes on the test environment. > > > How can we be sure that new changes in TCP discovery Ignite's > > > component won't break the Azure module? I don't think we should allow > > > such a practice at all, so the AWS and GCE is not a good example here. > > > Probably we don't know are they work correctly at all because they are > > > don't even used by users. > > > > > > On Mon, 6 Sept 2021 at 21:18, Atri Sharma wrote: > > > > > > > > Maxim, > > > > > > > > I thought Pavel has already reported that the tests run fine with a > > > > valid Azure account? > > > > > > > > On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov > > > wrote: > > > > > > > > > > Folks, > > > > > > > > > > Sorry for the reminder :-) > > > > > > > > > > This issue [1] still blocks the release and the development. There is > > > > > a week that has passed, however, the issue is still not resolved and > > > > > cannot be validated within a reasonable time frame. Trust is a good > > > > > thing and all the community members should trust each other, but we > > > > > still have the RTC procedure and I don't think we should refuse оf it > > > > > just because of trust and all of us are highly qualified engineers. > > > > > This is my humble opinion, but I don't think that this issue [1] is a > > > > > good candidate to include the release since additional checks are > > > > > still required. Things like this can quickly turn into dead code (like > > > > > the AWS and GCE modules do) and it's better to add additional tests > > > > > for it prior to release them. > > > > > > > > > > So here is the plan: > > > > > > > > > > - revert [1] from the release 2.11 branch (I'll do it tomorrow) > > > > > - commit the [1] to the master branch (success build is enough > > > > > verification for this at this moment) > > > > > - create and configure TC with a technical azure account to test such > > > module > > > > > - initiate a discussion to move Azure, AWS, GCE modules to the > > > > > ignite-extension project > > > > > - do everything above prior to the 2.12 release. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > > > > > > > > > > > On Fri, 3 Sept 2021 at 18:36, Pavel Pereslegin > > > wrote: > > > > > > > > > > > > Atri, > > > > > > > > > > > > > Anyone with azure account should be able to test it > > > > > > > > > > > > I checked the test included in the module with an Azure account (as > > > > > > I > > > > > > mentioned in Jira), it passes successfully. But I'm not sure if this > > > > > > is enough. > > > > > > > > > > > > пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov : > > > > > > > > > > > > > > Atri. > > > > > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Denis, if Atri looked at the changes why didn't he left any comments or review approval? Only the ipfinder test was checked in Azure, it is essentially synthetic, is it enough? As far as I understand, we have to deploy Ignite itself in the cloud and play with it to make sure it works, unfortunately, I do not have the competence, as well as free time to study how to do this, so we asked for help. вт, 7 сент. 2021 г. в 14:23, Denis Magda : > > Maxim, > > Regardless of a lack of automated testing in a real environment, our AWS, > GCE and other modules are used actively by the users and we don't receive > issue reports. Here are the numbers: > >- AWS - 7000 *monthly* Maven downloads on average >- GCE - 350 downloads >- Kubernetes - 6000 downloads > > So they are far from dead. > > I think it's not corrected to skip the Azure integration from the release > only because it follows the same testing approach. If you propose to change > it, then let's do it outside of this discussion and for all the modules. > The first step would be to find a sponsor who is ready to provision > resources on the cloud environments (that was the main obstacle when the > current test suites were being created). > > I don't know, currently, I'm not able to verify the results of this > > execution. > > > The module was verified by Atri and Pavel. This looks enough. If you have > doubts, you can also double-check the code and work with Atri in case any > issue arises. > > -- > Denis > > - > Denis > > On Mon, Sep 6, 2021 at 2:50 PM Maxim Muzafarov wrote: > > > Atri, > > > > I don't know, currently, I'm not able to verify the results of this > > execution. For instance, we have the TcpDiscoveryZookeeperIpFinder and > > it has the corresponding test suite on the TeamCity server, so when I > > make code changes I can verify these changes on the test environment. > > How can we be sure that new changes in TCP discovery Ignite's > > component won't break the Azure module? I don't think we should allow > > such a practice at all, so the AWS and GCE is not a good example here. > > Probably we don't know are they work correctly at all because they are > > don't even used by users. > > > > On Mon, 6 Sept 2021 at 21:18, Atri Sharma wrote: > > > > > > Maxim, > > > > > > I thought Pavel has already reported that the tests run fine with a > > > valid Azure account? > > > > > > On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov > > wrote: > > > > > > > > Folks, > > > > > > > > Sorry for the reminder :-) > > > > > > > > This issue [1] still blocks the release and the development. There is > > > > a week that has passed, however, the issue is still not resolved and > > > > cannot be validated within a reasonable time frame. Trust is a good > > > > thing and all the community members should trust each other, but we > > > > still have the RTC procedure and I don't think we should refuse оf it > > > > just because of trust and all of us are highly qualified engineers. > > > > This is my humble opinion, but I don't think that this issue [1] is a > > > > good candidate to include the release since additional checks are > > > > still required. Things like this can quickly turn into dead code (like > > > > the AWS and GCE modules do) and it's better to add additional tests > > > > for it prior to release them. > > > > > > > > So here is the plan: > > > > > > > > - revert [1] from the release 2.11 branch (I'll do it tomorrow) > > > > - commit the [1] to the master branch (success build is enough > > > > verification for this at this moment) > > > > - create and configure TC with a technical azure account to test such > > module > > > > - initiate a discussion to move Azure, AWS, GCE modules to the > > > > ignite-extension project > > > > - do everything above prior to the 2.12 release. > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > > > > > > > On Fri, 3 Sept 2021 at 18:36, Pavel Pereslegin > > wrote: > > > > > > > > > > Atri, > > > > > > > > > > > Anyone with azure account should be able to test it > > > > > > > > > > I checked the test included in the module with an Azure account (as I > > > > > mentioned in Jira), it passes successfully. But I'm not sure if this > > > > > is enough. > > > > > > > > > > пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov : > > > > > > > > > > > > Atri. > > > > > > > > > > > > Right now code can’t be tested because it doesn’t compile. > > > > > > > > > > > > > 3 сент. 2021 г., в 17:42, Atri Sharma > > написал(а): > > > > > > > > > > > > > > I am not sure why is it can be tested by few members? > > > > > > > > > > > > > > Anyone with azure account should be able to test it > > > > > > > > > > > > > > On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, > > wrote: > > > > > > > > > > > > > >> Folks, > > > > > > >> > > > > > > >> The GCP and AWS should also be moved to extensions, but this is > > a > > > > > > >> discussion for another topic. > > > > > > >> > > > > > > >> I trust you
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Maxim, Regardless of a lack of automated testing in a real environment, our AWS, GCE and other modules are used actively by the users and we don't receive issue reports. Here are the numbers: - AWS - 7000 *monthly* Maven downloads on average - GCE - 350 downloads - Kubernetes - 6000 downloads So they are far from dead. I think it's not corrected to skip the Azure integration from the release only because it follows the same testing approach. If you propose to change it, then let's do it outside of this discussion and for all the modules. The first step would be to find a sponsor who is ready to provision resources on the cloud environments (that was the main obstacle when the current test suites were being created). I don't know, currently, I'm not able to verify the results of this > execution. The module was verified by Atri and Pavel. This looks enough. If you have doubts, you can also double-check the code and work with Atri in case any issue arises. -- Denis - Denis On Mon, Sep 6, 2021 at 2:50 PM Maxim Muzafarov wrote: > Atri, > > I don't know, currently, I'm not able to verify the results of this > execution. For instance, we have the TcpDiscoveryZookeeperIpFinder and > it has the corresponding test suite on the TeamCity server, so when I > make code changes I can verify these changes on the test environment. > How can we be sure that new changes in TCP discovery Ignite's > component won't break the Azure module? I don't think we should allow > such a practice at all, so the AWS and GCE is not a good example here. > Probably we don't know are they work correctly at all because they are > don't even used by users. > > On Mon, 6 Sept 2021 at 21:18, Atri Sharma wrote: > > > > Maxim, > > > > I thought Pavel has already reported that the tests run fine with a > > valid Azure account? > > > > On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov > wrote: > > > > > > Folks, > > > > > > Sorry for the reminder :-) > > > > > > This issue [1] still blocks the release and the development. There is > > > a week that has passed, however, the issue is still not resolved and > > > cannot be validated within a reasonable time frame. Trust is a good > > > thing and all the community members should trust each other, but we > > > still have the RTC procedure and I don't think we should refuse оf it > > > just because of trust and all of us are highly qualified engineers. > > > This is my humble opinion, but I don't think that this issue [1] is a > > > good candidate to include the release since additional checks are > > > still required. Things like this can quickly turn into dead code (like > > > the AWS and GCE modules do) and it's better to add additional tests > > > for it prior to release them. > > > > > > So here is the plan: > > > > > > - revert [1] from the release 2.11 branch (I'll do it tomorrow) > > > - commit the [1] to the master branch (success build is enough > > > verification for this at this moment) > > > - create and configure TC with a technical azure account to test such > module > > > - initiate a discussion to move Azure, AWS, GCE modules to the > > > ignite-extension project > > > - do everything above prior to the 2.12 release. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > > > On Fri, 3 Sept 2021 at 18:36, Pavel Pereslegin > wrote: > > > > > > > > Atri, > > > > > > > > > Anyone with azure account should be able to test it > > > > > > > > I checked the test included in the module with an Azure account (as I > > > > mentioned in Jira), it passes successfully. But I'm not sure if this > > > > is enough. > > > > > > > > пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov : > > > > > > > > > > Atri. > > > > > > > > > > Right now code can’t be tested because it doesn’t compile. > > > > > > > > > > > 3 сент. 2021 г., в 17:42, Atri Sharma > написал(а): > > > > > > > > > > > > I am not sure why is it can be tested by few members? > > > > > > > > > > > > Anyone with azure account should be able to test it > > > > > > > > > > > > On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, > wrote: > > > > > > > > > > > >> Folks, > > > > > >> > > > > > >> The GCP and AWS should also be moved to extensions, but this is > a > > > > > >> discussion for another topic. > > > > > >> > > > > > >> I trust you all :-) > > > > > >> But who can validate the patch [1]? This is a bad practice that > only a > > > > > >> few members be able to test the code. > > > > > >> > > > > > >> > > > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > >> > > > > > >> On Fri, 3 Sept 2021 at 16:43, Atri Sharma > wrote: > > > > > >>> > > > > > >>> It was extensively tested by myself (running the tests on an > actual Azure > > > > > >>> account and running an Ignite cluster using an Azure account) > and Ilya > > > > > >>> (thanks Ilya!) prior to merging it in the core > > > > > >>> > > > > > >>> On Fri, 3 Sep 2021, 18:50 Denis Magda, > wrote: > > > > > >>> > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Atri, I don't know, currently, I'm not able to verify the results of this execution. For instance, we have the TcpDiscoveryZookeeperIpFinder and it has the corresponding test suite on the TeamCity server, so when I make code changes I can verify these changes on the test environment. How can we be sure that new changes in TCP discovery Ignite's component won't break the Azure module? I don't think we should allow such a practice at all, so the AWS and GCE is not a good example here. Probably we don't know are they work correctly at all because they are don't even used by users. On Mon, 6 Sept 2021 at 21:18, Atri Sharma wrote: > > Maxim, > > I thought Pavel has already reported that the tests run fine with a > valid Azure account? > > On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov wrote: > > > > Folks, > > > > Sorry for the reminder :-) > > > > This issue [1] still blocks the release and the development. There is > > a week that has passed, however, the issue is still not resolved and > > cannot be validated within a reasonable time frame. Trust is a good > > thing and all the community members should trust each other, but we > > still have the RTC procedure and I don't think we should refuse оf it > > just because of trust and all of us are highly qualified engineers. > > This is my humble opinion, but I don't think that this issue [1] is a > > good candidate to include the release since additional checks are > > still required. Things like this can quickly turn into dead code (like > > the AWS and GCE modules do) and it's better to add additional tests > > for it prior to release them. > > > > So here is the plan: > > > > - revert [1] from the release 2.11 branch (I'll do it tomorrow) > > - commit the [1] to the master branch (success build is enough > > verification for this at this moment) > > - create and configure TC with a technical azure account to test such module > > - initiate a discussion to move Azure, AWS, GCE modules to the > > ignite-extension project > > - do everything above prior to the 2.12 release. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > On Fri, 3 Sept 2021 at 18:36, Pavel Pereslegin wrote: > > > > > > Atri, > > > > > > > Anyone with azure account should be able to test it > > > > > > I checked the test included in the module with an Azure account (as I > > > mentioned in Jira), it passes successfully. But I'm not sure if this > > > is enough. > > > > > > пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov : > > > > > > > > Atri. > > > > > > > > Right now code can’t be tested because it doesn’t compile. > > > > > > > > > 3 сент. 2021 г., в 17:42, Atri Sharma написал(а): > > > > > > > > > > I am not sure why is it can be tested by few members? > > > > > > > > > > Anyone with azure account should be able to test it > > > > > > > > > > On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, wrote: > > > > > > > > > >> Folks, > > > > >> > > > > >> The GCP and AWS should also be moved to extensions, but this is a > > > > >> discussion for another topic. > > > > >> > > > > >> I trust you all :-) > > > > >> But who can validate the patch [1]? This is a bad practice that only > > > > >> a > > > > >> few members be able to test the code. > > > > >> > > > > >> > > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > >> > > > > >> On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote: > > > > >>> > > > > >>> It was extensively tested by myself (running the tests on an actual > > > > >>> Azure > > > > >>> account and running an Ignite cluster using an Azure account) and > > > > >>> Ilya > > > > >>> (thanks Ilya!) prior to merging it in the core > > > > >>> > > > > >>> On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: > > > > >>> > > > > Disagree to exclude this contribution from the 2.11 release. As > > > > Atri > > > > explained, its implementation and testing approach is identical to > > > > the > > > > >> AWS, > > > > GCP and Kubernetes IP finders. > > > > If we want to move the modules to extensions and improve the > > > > testing > > > > approach, then it needs to be done for all similar components. > > > > > > > > Atri, have you tested the module in the cloud? If it works, then I > > > > >> don't > > > > see any reason why we need to have someone else double-checking > > > > this > > > > >> once > > > > again. This is the community, we need to trust each other. > > > > > > > > - > > > > Denis > > > > > > > > On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > > > > > > > > > I would argue that the module Co exists with the other IP > > > > > discovery > > > > modules > > > > > (such as GCP and AWS), which are part of core. > > > > > > > > > > In terms of tests, the azure module has exactly the same type of > > > > >> tests as > > > > > the other two modules mentioned above. > > > > > > > > > > On Fri, 3 Sep 2021,
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Maxim, I thought Pavel has already reported that the tests run fine with a valid Azure account? On Mon, Sep 6, 2021 at 11:10 PM Maxim Muzafarov wrote: > > Folks, > > Sorry for the reminder :-) > > This issue [1] still blocks the release and the development. There is > a week that has passed, however, the issue is still not resolved and > cannot be validated within a reasonable time frame. Trust is a good > thing and all the community members should trust each other, but we > still have the RTC procedure and I don't think we should refuse оf it > just because of trust and all of us are highly qualified engineers. > This is my humble opinion, but I don't think that this issue [1] is a > good candidate to include the release since additional checks are > still required. Things like this can quickly turn into dead code (like > the AWS and GCE modules do) and it's better to add additional tests > for it prior to release them. > > So here is the plan: > > - revert [1] from the release 2.11 branch (I'll do it tomorrow) > - commit the [1] to the master branch (success build is enough > verification for this at this moment) > - create and configure TC with a technical azure account to test such module > - initiate a discussion to move Azure, AWS, GCE modules to the > ignite-extension project > - do everything above prior to the 2.12 release. > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > On Fri, 3 Sept 2021 at 18:36, Pavel Pereslegin wrote: > > > > Atri, > > > > > Anyone with azure account should be able to test it > > > > I checked the test included in the module with an Azure account (as I > > mentioned in Jira), it passes successfully. But I'm not sure if this > > is enough. > > > > пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov : > > > > > > Atri. > > > > > > Right now code can’t be tested because it doesn’t compile. > > > > > > > 3 сент. 2021 г., в 17:42, Atri Sharma написал(а): > > > > > > > > I am not sure why is it can be tested by few members? > > > > > > > > Anyone with azure account should be able to test it > > > > > > > > On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, wrote: > > > > > > > >> Folks, > > > >> > > > >> The GCP and AWS should also be moved to extensions, but this is a > > > >> discussion for another topic. > > > >> > > > >> I trust you all :-) > > > >> But who can validate the patch [1]? This is a bad practice that only a > > > >> few members be able to test the code. > > > >> > > > >> > > > >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > >> > > > >> On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote: > > > >>> > > > >>> It was extensively tested by myself (running the tests on an actual > > > >>> Azure > > > >>> account and running an Ignite cluster using an Azure account) and Ilya > > > >>> (thanks Ilya!) prior to merging it in the core > > > >>> > > > >>> On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: > > > >>> > > > Disagree to exclude this contribution from the 2.11 release. As Atri > > > explained, its implementation and testing approach is identical to > > > the > > > >> AWS, > > > GCP and Kubernetes IP finders. > > > If we want to move the modules to extensions and improve the testing > > > approach, then it needs to be done for all similar components. > > > > > > Atri, have you tested the module in the cloud? If it works, then I > > > >> don't > > > see any reason why we need to have someone else double-checking this > > > >> once > > > again. This is the community, we need to trust each other. > > > > > > - > > > Denis > > > > > > On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > > > > > > > I would argue that the module Co exists with the other IP discovery > > > modules > > > > (such as GCP and AWS), which are part of core. > > > > > > > > In terms of tests, the azure module has exactly the same type of > > > >> tests as > > > > the other two modules mentioned above. > > > > > > > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, > > > >> wrote: > > > > > > > >> Folks, > > > >> > > > >> The patch [1] for the azure module seems to be ready for review, > > > >> however, there are still some questions that exist: > > > >> - Do we have a technical account in azure to test the moude on TC? > > > >> Manual testing for such changes is really annoying. > > > >> - Is there any reason to add these changes to the main Apache > > > >> Ignite > > > >> project? Why not extensions? > > > >> - It seems there is a lack of tests for this module. > > > >> > > > >> According to the mentions above, what do you think about moving > > > >> this > > > >> functionality to the next 2.12 release to solve all the questions > > > >> without a rush? I propose to revert the changes related to the > > > >> azure > > > >> functionality from the 2.11 branch. > > > >> > > > >> > > > >> [1]
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, Sorry for the reminder :-) This issue [1] still blocks the release and the development. There is a week that has passed, however, the issue is still not resolved and cannot be validated within a reasonable time frame. Trust is a good thing and all the community members should trust each other, but we still have the RTC procedure and I don't think we should refuse оf it just because of trust and all of us are highly qualified engineers. This is my humble opinion, but I don't think that this issue [1] is a good candidate to include the release since additional checks are still required. Things like this can quickly turn into dead code (like the AWS and GCE modules do) and it's better to add additional tests for it prior to release them. So here is the plan: - revert [1] from the release 2.11 branch (I'll do it tomorrow) - commit the [1] to the master branch (success build is enough verification for this at this moment) - create and configure TC with a technical azure account to test such module - initiate a discussion to move Azure, AWS, GCE modules to the ignite-extension project - do everything above prior to the 2.12 release. [1] https://issues.apache.org/jira/browse/IGNITE-15388 On Fri, 3 Sept 2021 at 18:36, Pavel Pereslegin wrote: > > Atri, > > > Anyone with azure account should be able to test it > > I checked the test included in the module with an Azure account (as I > mentioned in Jira), it passes successfully. But I'm not sure if this > is enough. > > пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov : > > > > Atri. > > > > Right now code can’t be tested because it doesn’t compile. > > > > > 3 сент. 2021 г., в 17:42, Atri Sharma написал(а): > > > > > > I am not sure why is it can be tested by few members? > > > > > > Anyone with azure account should be able to test it > > > > > > On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, wrote: > > > > > >> Folks, > > >> > > >> The GCP and AWS should also be moved to extensions, but this is a > > >> discussion for another topic. > > >> > > >> I trust you all :-) > > >> But who can validate the patch [1]? This is a bad practice that only a > > >> few members be able to test the code. > > >> > > >> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > >> > > >> On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote: > > >>> > > >>> It was extensively tested by myself (running the tests on an actual > > >>> Azure > > >>> account and running an Ignite cluster using an Azure account) and Ilya > > >>> (thanks Ilya!) prior to merging it in the core > > >>> > > >>> On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: > > >>> > > Disagree to exclude this contribution from the 2.11 release. As Atri > > explained, its implementation and testing approach is identical to the > > >> AWS, > > GCP and Kubernetes IP finders. > > If we want to move the modules to extensions and improve the testing > > approach, then it needs to be done for all similar components. > > > > Atri, have you tested the module in the cloud? If it works, then I > > >> don't > > see any reason why we need to have someone else double-checking this > > >> once > > again. This is the community, we need to trust each other. > > > > - > > Denis > > > > On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > > > > > I would argue that the module Co exists with the other IP discovery > > modules > > > (such as GCP and AWS), which are part of core. > > > > > > In terms of tests, the azure module has exactly the same type of > > >> tests as > > > the other two modules mentioned above. > > > > > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, > > >> wrote: > > > > > >> Folks, > > >> > > >> The patch [1] for the azure module seems to be ready for review, > > >> however, there are still some questions that exist: > > >> - Do we have a technical account in azure to test the moude on TC? > > >> Manual testing for such changes is really annoying. > > >> - Is there any reason to add these changes to the main Apache > > >> Ignite > > >> project? Why not extensions? > > >> - It seems there is a lack of tests for this module. > > >> > > >> According to the mentions above, what do you think about moving > > >> this > > >> functionality to the next 2.12 release to solve all the questions > > >> without a rush? I propose to revert the changes related to the > > >> azure > > >> functionality from the 2.11 branch. > > >> > > >> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > >> > > >> On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov > > wrote: > > >>> > > >>> We had a separate discussion with Max and Alex, so I tend to > > >> agree > > that > > >>> both issues are blockers. > > >>> > > >>> Sincerely, > > >>> Dmitriy Pavlov > > >>> > > >>> пт, 27 авг. 2021 г. в 16:41, Alexey
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Atri, > Anyone with azure account should be able to test it I checked the test included in the module with an Azure account (as I mentioned in Jira), it passes successfully. But I'm not sure if this is enough. пт, 3 сент. 2021 г. в 17:48, Nikolay Izhikov : > > Atri. > > Right now code can’t be tested because it doesn’t compile. > > > 3 сент. 2021 г., в 17:42, Atri Sharma написал(а): > > > > I am not sure why is it can be tested by few members? > > > > Anyone with azure account should be able to test it > > > > On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, wrote: > > > >> Folks, > >> > >> The GCP and AWS should also be moved to extensions, but this is a > >> discussion for another topic. > >> > >> I trust you all :-) > >> But who can validate the patch [1]? This is a bad practice that only a > >> few members be able to test the code. > >> > >> > >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 > >> > >> On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote: > >>> > >>> It was extensively tested by myself (running the tests on an actual Azure > >>> account and running an Ignite cluster using an Azure account) and Ilya > >>> (thanks Ilya!) prior to merging it in the core > >>> > >>> On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: > >>> > Disagree to exclude this contribution from the 2.11 release. As Atri > explained, its implementation and testing approach is identical to the > >> AWS, > GCP and Kubernetes IP finders. > If we want to move the modules to extensions and improve the testing > approach, then it needs to be done for all similar components. > > Atri, have you tested the module in the cloud? If it works, then I > >> don't > see any reason why we need to have someone else double-checking this > >> once > again. This is the community, we need to trust each other. > > - > Denis > > On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > > > I would argue that the module Co exists with the other IP discovery > modules > > (such as GCP and AWS), which are part of core. > > > > In terms of tests, the azure module has exactly the same type of > >> tests as > > the other two modules mentioned above. > > > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, > >> wrote: > > > >> Folks, > >> > >> The patch [1] for the azure module seems to be ready for review, > >> however, there are still some questions that exist: > >> - Do we have a technical account in azure to test the moude on TC? > >> Manual testing for such changes is really annoying. > >> - Is there any reason to add these changes to the main Apache > >> Ignite > >> project? Why not extensions? > >> - It seems there is a lack of tests for this module. > >> > >> According to the mentions above, what do you think about moving > >> this > >> functionality to the next 2.12 release to solve all the questions > >> without a rush? I propose to revert the changes related to the > >> azure > >> functionality from the 2.11 branch. > >> > >> > >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 > >> > >> On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov > wrote: > >>> > >>> We had a separate discussion with Max and Alex, so I tend to > >> agree > that > >>> both issues are blockers. > >>> > >>> Sincerely, > >>> Dmitriy Pavlov > >>> > >>> пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov < > >> olive.c...@gmail.com>: > >>> > Hi, Maxim! > > These issues really block release. So we should wait fixes. > > On 2021/08/27 12:46:24, Maxim Muzafarov > >> wrote: > > Folks, > > > > > > I've been faced these issues, which seems to be a blocker > >> for the > > release. Please, take a look and share your thoughts. > > > > The server node fails when the client node with the higher > >> java > > version connects to it [1]. > > The Apache Ignite build fails with missing dependency [2]. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov < > >> mmu...@apache.org> > >> wrote: > >> > >> +1 > >> > >> On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky < > > ivanda...@gmail.com> > wrote: > >>> > >>> I suppose, that > >> https://issues.apache.org/jira/browse/IGNITE-15274 > is a > >>> blocker. > >>> Fix is quite easy and straightforward > >>> > >>> пн, 2 авг. 2021 г. в 03:11, Igor Sapego < > >> isap...@apache.org > > : > >>> > Cherry-picked to release branch. > > Best Regards, > Igor > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Atri. Right now code can’t be tested because it doesn’t compile. > 3 сент. 2021 г., в 17:42, Atri Sharma написал(а): > > I am not sure why is it can be tested by few members? > > Anyone with azure account should be able to test it > > On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, wrote: > >> Folks, >> >> The GCP and AWS should also be moved to extensions, but this is a >> discussion for another topic. >> >> I trust you all :-) >> But who can validate the patch [1]? This is a bad practice that only a >> few members be able to test the code. >> >> >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 >> >> On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote: >>> >>> It was extensively tested by myself (running the tests on an actual Azure >>> account and running an Ignite cluster using an Azure account) and Ilya >>> (thanks Ilya!) prior to merging it in the core >>> >>> On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: >>> Disagree to exclude this contribution from the 2.11 release. As Atri explained, its implementation and testing approach is identical to the >> AWS, GCP and Kubernetes IP finders. If we want to move the modules to extensions and improve the testing approach, then it needs to be done for all similar components. Atri, have you tested the module in the cloud? If it works, then I >> don't see any reason why we need to have someone else double-checking this >> once again. This is the community, we need to trust each other. - Denis On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > I would argue that the module Co exists with the other IP discovery modules > (such as GCP and AWS), which are part of core. > > In terms of tests, the azure module has exactly the same type of >> tests as > the other two modules mentioned above. > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, >> wrote: > >> Folks, >> >> The patch [1] for the azure module seems to be ready for review, >> however, there are still some questions that exist: >> - Do we have a technical account in azure to test the moude on TC? >> Manual testing for such changes is really annoying. >> - Is there any reason to add these changes to the main Apache >> Ignite >> project? Why not extensions? >> - It seems there is a lack of tests for this module. >> >> According to the mentions above, what do you think about moving >> this >> functionality to the next 2.12 release to solve all the questions >> without a rush? I propose to revert the changes related to the >> azure >> functionality from the 2.11 branch. >> >> >> [1] https://issues.apache.org/jira/browse/IGNITE-15388 >> >> On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov wrote: >>> >>> We had a separate discussion with Max and Alex, so I tend to >> agree that >>> both issues are blockers. >>> >>> Sincerely, >>> Dmitriy Pavlov >>> >>> пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov < >> olive.c...@gmail.com>: >>> Hi, Maxim! These issues really block release. So we should wait fixes. On 2021/08/27 12:46:24, Maxim Muzafarov >> wrote: > Folks, > > > I've been faced these issues, which seems to be a blocker >> for the > release. Please, take a look and share your thoughts. > > The server node fails when the client node with the higher >> java > version connects to it [1]. > The Apache Ignite build fails with missing dependency [2]. > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov < >> mmu...@apache.org> >> wrote: >> >> +1 >> >> On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky < > ivanda...@gmail.com> wrote: >>> >>> I suppose, that >> https://issues.apache.org/jira/browse/IGNITE-15274 is a >>> blocker. >>> Fix is quite easy and straightforward >>> >>> пн, 2 авг. 2021 г. в 03:11, Igor Sapego < >> isap...@apache.org > : >>> Cherry-picked to release branch. Best Regards, Igor On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < olive.c...@gmail.com> wrote: > Ok, I think we should add [1] to 2.11 release. Can >> you cherry-pick it to > release branch? > [1] >> https://issues.apache.org/jira/browse/IGNITE-14815 > > On 2021/07/30 02:25:25, Igor Sapego < >> isap...@apache.org> >> wrote: >> I'm fine with any of these two solutions.
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
I am not sure why is it can be tested by few members? Anyone with azure account should be able to test it On Fri, 3 Sep 2021, 19:29 Maxim Muzafarov, wrote: > Folks, > > The GCP and AWS should also be moved to extensions, but this is a > discussion for another topic. > > I trust you all :-) > But who can validate the patch [1]? This is a bad practice that only a > few members be able to test the code. > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote: > > > > It was extensively tested by myself (running the tests on an actual Azure > > account and running an Ignite cluster using an Azure account) and Ilya > > (thanks Ilya!) prior to merging it in the core > > > > On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: > > > > > Disagree to exclude this contribution from the 2.11 release. As Atri > > > explained, its implementation and testing approach is identical to the > AWS, > > > GCP and Kubernetes IP finders. > > > If we want to move the modules to extensions and improve the testing > > > approach, then it needs to be done for all similar components. > > > > > > Atri, have you tested the module in the cloud? If it works, then I > don't > > > see any reason why we need to have someone else double-checking this > once > > > again. This is the community, we need to trust each other. > > > > > > - > > > Denis > > > > > > On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > > > > > > > I would argue that the module Co exists with the other IP discovery > > > modules > > > > (such as GCP and AWS), which are part of core. > > > > > > > > In terms of tests, the azure module has exactly the same type of > tests as > > > > the other two modules mentioned above. > > > > > > > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, > wrote: > > > > > > > > > Folks, > > > > > > > > > > The patch [1] for the azure module seems to be ready for review, > > > > > however, there are still some questions that exist: > > > > > - Do we have a technical account in azure to test the moude on TC? > > > > > Manual testing for such changes is really annoying. > > > > > - Is there any reason to add these changes to the main Apache > Ignite > > > > > project? Why not extensions? > > > > > - It seems there is a lack of tests for this module. > > > > > > > > > > According to the mentions above, what do you think about moving > this > > > > > functionality to the next 2.12 release to solve all the questions > > > > > without a rush? I propose to revert the changes related to the > azure > > > > > functionality from the 2.11 branch. > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov > > > wrote: > > > > > > > > > > > > We had a separate discussion with Max and Alex, so I tend to > agree > > > that > > > > > > both issues are blockers. > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > > > > > пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov < > olive.c...@gmail.com>: > > > > > > > > > > > > > Hi, Maxim! > > > > > > > > > > > > > > These issues really block release. So we should wait fixes. > > > > > > > > > > > > > > On 2021/08/27 12:46:24, Maxim Muzafarov > wrote: > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > I've been faced these issues, which seems to be a blocker > for the > > > > > > > > release. Please, take a look and share your thoughts. > > > > > > > > > > > > > > > > The server node fails when the client node with the higher > java > > > > > > > > version connects to it [1]. > > > > > > > > The Apache Ignite build fails with missing dependency [2]. > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov < > mmu...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky < > > > > ivanda...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > I suppose, that > > > > > https://issues.apache.org/jira/browse/IGNITE-15274 > > > > > > > is a > > > > > > > > > > blocker. > > > > > > > > > > Fix is quite easy and straightforward > > > > > > > > > > > > > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego < > isap...@apache.org > > > >: > > > > > > > > > > > > > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > > > > > > > olive.c...@gmail.com> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can > you > > > > > > > cherry-pick it to > > > > > > > > > > > > release
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, I'd like to mention that currently THE BUILD is broken not only for the release branch but for the master also. It's true that the TC has cached the artefacts, so we don't see broken builds but how to build the Apache Ignite locally? I'm not able to do so. On Fri, 3 Sept 2021 at 16:59, Maxim Muzafarov wrote: > > Folks, > > The GCP and AWS should also be moved to extensions, but this is a > discussion for another topic. > > I trust you all :-) > But who can validate the patch [1]? This is a bad practice that only a > few members be able to test the code. > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote: > > > > It was extensively tested by myself (running the tests on an actual Azure > > account and running an Ignite cluster using an Azure account) and Ilya > > (thanks Ilya!) prior to merging it in the core > > > > On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: > > > > > Disagree to exclude this contribution from the 2.11 release. As Atri > > > explained, its implementation and testing approach is identical to the > > > AWS, > > > GCP and Kubernetes IP finders. > > > If we want to move the modules to extensions and improve the testing > > > approach, then it needs to be done for all similar components. > > > > > > Atri, have you tested the module in the cloud? If it works, then I don't > > > see any reason why we need to have someone else double-checking this once > > > again. This is the community, we need to trust each other. > > > > > > - > > > Denis > > > > > > On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > > > > > > > I would argue that the module Co exists with the other IP discovery > > > modules > > > > (such as GCP and AWS), which are part of core. > > > > > > > > In terms of tests, the azure module has exactly the same type of tests > > > > as > > > > the other two modules mentioned above. > > > > > > > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, wrote: > > > > > > > > > Folks, > > > > > > > > > > The patch [1] for the azure module seems to be ready for review, > > > > > however, there are still some questions that exist: > > > > > - Do we have a technical account in azure to test the moude on TC? > > > > > Manual testing for such changes is really annoying. > > > > > - Is there any reason to add these changes to the main Apache Ignite > > > > > project? Why not extensions? > > > > > - It seems there is a lack of tests for this module. > > > > > > > > > > According to the mentions above, what do you think about moving this > > > > > functionality to the next 2.12 release to solve all the questions > > > > > without a rush? I propose to revert the changes related to the azure > > > > > functionality from the 2.11 branch. > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov > > > wrote: > > > > > > > > > > > > We had a separate discussion with Max and Alex, so I tend to agree > > > that > > > > > > both issues are blockers. > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > > > > > пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov : > > > > > > > > > > > > > Hi, Maxim! > > > > > > > > > > > > > > These issues really block release. So we should wait fixes. > > > > > > > > > > > > > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > I've been faced these issues, which seems to be a blocker for > > > > > > > > the > > > > > > > > release. Please, take a look and share your thoughts. > > > > > > > > > > > > > > > > The server node fails when the client node with the higher java > > > > > > > > version connects to it [1]. > > > > > > > > The Apache Ignite build fails with missing dependency [2]. > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov > > > > > wrote: > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky < > > > > ivanda...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > I suppose, that > > > > > https://issues.apache.org/jira/browse/IGNITE-15274 > > > > > > > is a > > > > > > > > > > blocker. > > > > > > > > > > Fix is quite easy and straightforward > > > > > > > > > > > > > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego > > >: > > > > > > > > > > > > > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > > > > > > > olive.c...@gmail.com> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Ok, I think we
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, The GCP and AWS should also be moved to extensions, but this is a discussion for another topic. I trust you all :-) But who can validate the patch [1]? This is a bad practice that only a few members be able to test the code. [1] https://issues.apache.org/jira/browse/IGNITE-15388 On Fri, 3 Sept 2021 at 16:43, Atri Sharma wrote: > > It was extensively tested by myself (running the tests on an actual Azure > account and running an Ignite cluster using an Azure account) and Ilya > (thanks Ilya!) prior to merging it in the core > > On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: > > > Disagree to exclude this contribution from the 2.11 release. As Atri > > explained, its implementation and testing approach is identical to the AWS, > > GCP and Kubernetes IP finders. > > If we want to move the modules to extensions and improve the testing > > approach, then it needs to be done for all similar components. > > > > Atri, have you tested the module in the cloud? If it works, then I don't > > see any reason why we need to have someone else double-checking this once > > again. This is the community, we need to trust each other. > > > > - > > Denis > > > > On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > > > > > I would argue that the module Co exists with the other IP discovery > > modules > > > (such as GCP and AWS), which are part of core. > > > > > > In terms of tests, the azure module has exactly the same type of tests as > > > the other two modules mentioned above. > > > > > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, wrote: > > > > > > > Folks, > > > > > > > > The patch [1] for the azure module seems to be ready for review, > > > > however, there are still some questions that exist: > > > > - Do we have a technical account in azure to test the moude on TC? > > > > Manual testing for such changes is really annoying. > > > > - Is there any reason to add these changes to the main Apache Ignite > > > > project? Why not extensions? > > > > - It seems there is a lack of tests for this module. > > > > > > > > According to the mentions above, what do you think about moving this > > > > functionality to the next 2.12 release to solve all the questions > > > > without a rush? I propose to revert the changes related to the azure > > > > functionality from the 2.11 branch. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov > > wrote: > > > > > > > > > > We had a separate discussion with Max and Alex, so I tend to agree > > that > > > > > both issues are blockers. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov : > > > > > > > > > > > Hi, Maxim! > > > > > > > > > > > > These issues really block release. So we should wait fixes. > > > > > > > > > > > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > I've been faced these issues, which seems to be a blocker for the > > > > > > > release. Please, take a look and share your thoughts. > > > > > > > > > > > > > > The server node fails when the client node with the higher java > > > > > > > version connects to it [1]. > > > > > > > The Apache Ignite build fails with missing dependency [2]. > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov > > > > wrote: > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky < > > > ivanda...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > > > > I suppose, that > > > > https://issues.apache.org/jira/browse/IGNITE-15274 > > > > > > is a > > > > > > > > > blocker. > > > > > > > > > Fix is quite easy and straightforward > > > > > > > > > > > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego > >: > > > > > > > > > > > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > > > > > > olive.c...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you > > > > > > cherry-pick it to > > > > > > > > > > > release branch? > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego > > > > wrote: > > > > > > > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
It was extensively tested by myself (running the tests on an actual Azure account and running an Ignite cluster using an Azure account) and Ilya (thanks Ilya!) prior to merging it in the core On Fri, 3 Sep 2021, 18:50 Denis Magda, wrote: > Disagree to exclude this contribution from the 2.11 release. As Atri > explained, its implementation and testing approach is identical to the AWS, > GCP and Kubernetes IP finders. > If we want to move the modules to extensions and improve the testing > approach, then it needs to be done for all similar components. > > Atri, have you tested the module in the cloud? If it works, then I don't > see any reason why we need to have someone else double-checking this once > again. This is the community, we need to trust each other. > > - > Denis > > On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > > > I would argue that the module Co exists with the other IP discovery > modules > > (such as GCP and AWS), which are part of core. > > > > In terms of tests, the azure module has exactly the same type of tests as > > the other two modules mentioned above. > > > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, wrote: > > > > > Folks, > > > > > > The patch [1] for the azure module seems to be ready for review, > > > however, there are still some questions that exist: > > > - Do we have a technical account in azure to test the moude on TC? > > > Manual testing for such changes is really annoying. > > > - Is there any reason to add these changes to the main Apache Ignite > > > project? Why not extensions? > > > - It seems there is a lack of tests for this module. > > > > > > According to the mentions above, what do you think about moving this > > > functionality to the next 2.12 release to solve all the questions > > > without a rush? I propose to revert the changes related to the azure > > > functionality from the 2.11 branch. > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov > wrote: > > > > > > > > We had a separate discussion with Max and Alex, so I tend to agree > that > > > > both issues are blockers. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov : > > > > > > > > > Hi, Maxim! > > > > > > > > > > These issues really block release. So we should wait fixes. > > > > > > > > > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > > > > > Folks, > > > > > > > > > > > > > > > > > > I've been faced these issues, which seems to be a blocker for the > > > > > > release. Please, take a look and share your thoughts. > > > > > > > > > > > > The server node fails when the client node with the higher java > > > > > > version connects to it [1]. > > > > > > The Apache Ignite build fails with missing dependency [2]. > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov > > > wrote: > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky < > > ivanda...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > > > I suppose, that > > > https://issues.apache.org/jira/browse/IGNITE-15274 > > > > > is a > > > > > > > > blocker. > > > > > > > > Fix is quite easy and straightforward > > > > > > > > > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego >: > > > > > > > > > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > > > > > olive.c...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you > > > > > cherry-pick it to > > > > > > > > > > release branch? > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego > > > wrote: > > > > > > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > > > > > > ilya.kasnach...@gmail.com> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > > > > > > > > > I think it does make sense to include changes which > > will > > > let > > > > > us avoid > > > > > > > > > > > > migration issues in the future. > > > > > > > > > > > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete > > change > > > > > from 2.11 in > > > > > > > > > > order > > > > > > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees > > > and RE > > > > > thinks > > > > > > > > > > this is > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Disagree to exclude this contribution from the 2.11 release. As Atri explained, its implementation and testing approach is identical to the AWS, GCP and Kubernetes IP finders. If we want to move the modules to extensions and improve the testing approach, then it needs to be done for all similar components. Atri, have you tested the module in the cloud? If it works, then I don't see any reason why we need to have someone else double-checking this once again. This is the community, we need to trust each other. - Denis On Fri, Sep 3, 2021 at 9:15 AM Atri Sharma wrote: > I would argue that the module Co exists with the other IP discovery modules > (such as GCP and AWS), which are part of core. > > In terms of tests, the azure module has exactly the same type of tests as > the other two modules mentioned above. > > On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, wrote: > > > Folks, > > > > The patch [1] for the azure module seems to be ready for review, > > however, there are still some questions that exist: > > - Do we have a technical account in azure to test the moude on TC? > > Manual testing for such changes is really annoying. > > - Is there any reason to add these changes to the main Apache Ignite > > project? Why not extensions? > > - It seems there is a lack of tests for this module. > > > > According to the mentions above, what do you think about moving this > > functionality to the next 2.12 release to solve all the questions > > without a rush? I propose to revert the changes related to the azure > > functionality from the 2.11 branch. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov wrote: > > > > > > We had a separate discussion with Max and Alex, so I tend to agree that > > > both issues are blockers. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov : > > > > > > > Hi, Maxim! > > > > > > > > These issues really block release. So we should wait fixes. > > > > > > > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > > > > Folks, > > > > > > > > > > > > > > > I've been faced these issues, which seems to be a blocker for the > > > > > release. Please, take a look and share your thoughts. > > > > > > > > > > The server node fails when the client node with the higher java > > > > > version connects to it [1]. > > > > > The Apache Ignite build fails with missing dependency [2]. > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov > > wrote: > > > > > > > > > > > > +1 > > > > > > > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky < > ivanda...@gmail.com> > > > > wrote: > > > > > > > > > > > > > > I suppose, that > > https://issues.apache.org/jira/browse/IGNITE-15274 > > > > is a > > > > > > > blocker. > > > > > > > Fix is quite easy and straightforward > > > > > > > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > > > > olive.c...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you > > > > cherry-pick it to > > > > > > > > > release branch? > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego > > wrote: > > > > > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > > > > > ilya.kasnach...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > > > > > > > I think it does make sense to include changes which > will > > let > > > > us avoid > > > > > > > > > > > migration issues in the future. > > > > > > > > > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete > change > > > > from 2.11 in > > > > > > > > > order > > > > > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees > > and RE > > > > thinks > > > > > > > > > this is > > > > > > > > > > > the best course of action. > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > -- > > > > > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego < > > isap...@apache.org > > > > >: > > > > > > > > > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > > > > > > > > > It contains changes we could not introduce if we > > release > > > > ignite in > > > > > > > > > its
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
I would argue that the module Co exists with the other IP discovery modules (such as GCP and AWS), which are part of core. In terms of tests, the azure module has exactly the same type of tests as the other two modules mentioned above. On Fri, 3 Sep 2021, 17:54 Maxim Muzafarov, wrote: > Folks, > > The patch [1] for the azure module seems to be ready for review, > however, there are still some questions that exist: > - Do we have a technical account in azure to test the moude on TC? > Manual testing for such changes is really annoying. > - Is there any reason to add these changes to the main Apache Ignite > project? Why not extensions? > - It seems there is a lack of tests for this module. > > According to the mentions above, what do you think about moving this > functionality to the next 2.12 release to solve all the questions > without a rush? I propose to revert the changes related to the azure > functionality from the 2.11 branch. > > > [1] https://issues.apache.org/jira/browse/IGNITE-15388 > > On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov wrote: > > > > We had a separate discussion with Max and Alex, so I tend to agree that > > both issues are blockers. > > > > Sincerely, > > Dmitriy Pavlov > > > > пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov : > > > > > Hi, Maxim! > > > > > > These issues really block release. So we should wait fixes. > > > > > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > > > Folks, > > > > > > > > > > > > I've been faced these issues, which seems to be a blocker for the > > > > release. Please, take a look and share your thoughts. > > > > > > > > The server node fails when the client node with the higher java > > > > version connects to it [1]. > > > > The Apache Ignite build fails with missing dependency [2]. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov > wrote: > > > > > > > > > > +1 > > > > > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky > > > wrote: > > > > > > > > > > > > I suppose, that > https://issues.apache.org/jira/browse/IGNITE-15274 > > > is a > > > > > > blocker. > > > > > > Fix is quite easy and straightforward > > > > > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > > > > > Best Regards, > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > > > olive.c...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you > > > cherry-pick it to > > > > > > > > release branch? > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego > wrote: > > > > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > > > > ilya.kasnach...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > > > > > I think it does make sense to include changes which will > let > > > us avoid > > > > > > > > > > migration issues in the future. > > > > > > > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change > > > from 2.11 in > > > > > > > > order > > > > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees > and RE > > > thinks > > > > > > > > this is > > > > > > > > > > the best course of action. > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > -- > > > > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego < > isap...@apache.org > > > >: > > > > > > > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > > > > > > > It contains changes we could not introduce if we > release > > > ignite in > > > > > > > > its > > > > > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > > > > > olive.c...@gmail.com> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only > > > blockers. I > > > > > > > > may be > > > > > > > > > > > > wrong, but this ticket doesn't seem to be of that > kind. > > > > > > > > > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego < > isap...@apache.org> > > > wrote: > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > > > > > > > I suggest adding [1] to
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, The patch [1] for the azure module seems to be ready for review, however, there are still some questions that exist: - Do we have a technical account in azure to test the moude on TC? Manual testing for such changes is really annoying. - Is there any reason to add these changes to the main Apache Ignite project? Why not extensions? - It seems there is a lack of tests for this module. According to the mentions above, what do you think about moving this functionality to the next 2.12 release to solve all the questions without a rush? I propose to revert the changes related to the azure functionality from the 2.11 branch. [1] https://issues.apache.org/jira/browse/IGNITE-15388 On Fri, 27 Aug 2021 at 20:53, Dmitriy Pavlov wrote: > > We had a separate discussion with Max and Alex, so I tend to agree that > both issues are blockers. > > Sincerely, > Dmitriy Pavlov > > пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov : > > > Hi, Maxim! > > > > These issues really block release. So we should wait fixes. > > > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > > Folks, > > > > > > > > > I've been faced these issues, which seems to be a blocker for the > > > release. Please, take a look and share your thoughts. > > > > > > The server node fails when the client node with the higher java > > > version connects to it [1]. > > > The Apache Ignite build fails with missing dependency [2]. > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote: > > > > > > > > +1 > > > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky > > wrote: > > > > > > > > > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 > > is a > > > > > blocker. > > > > > Fix is quite easy and straightforward > > > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > > > Best Regards, > > > > > > Igor > > > > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > > olive.c...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you > > cherry-pick it to > > > > > > > release branch? > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > > > ilya.kasnach...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > > > I think it does make sense to include changes which will let > > us avoid > > > > > > > > > migration issues in the future. > > > > > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change > > from 2.11 in > > > > > > > order > > > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE > > thinks > > > > > > > this is > > > > > > > > > the best course of action. > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > -- > > > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego > >: > > > > > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > > > > > It contains changes we could not introduce if we release > > ignite in > > > > > > > its > > > > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > > > > olive.c...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only > > blockers. I > > > > > > > may be > > > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego > > wrote: > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because > > it > > > > > > contains > > > > > > > > > > > > changes to code introduced by [2], which is already > > included in > > > > > > > > > > release. > > > > > > > > > > > > > > > > > > > > > > > > [1] - > > https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > [2] - > > https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > > > > > mmu...@apache.org>
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
We had a separate discussion with Max and Alex, so I tend to agree that both issues are blockers. Sincerely, Dmitriy Pavlov пт, 27 авг. 2021 г. в 16:41, Alexey Gidaspov : > Hi, Maxim! > > These issues really block release. So we should wait fixes. > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > Folks, > > > > > > I've been faced these issues, which seems to be a blocker for the > > release. Please, take a look and share your thoughts. > > > > The server node fails when the client node with the higher java > > version connects to it [1]. > > The Apache Ignite build fails with missing dependency [2]. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote: > > > > > > +1 > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky > wrote: > > > > > > > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 > is a > > > > blocker. > > > > Fix is quite easy and straightforward > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > olive.c...@gmail.com> > > > > > wrote: > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you > cherry-pick it to > > > > > > release branch? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > > > Best Regards, > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > > ilya.kasnach...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > I think it does make sense to include changes which will let > us avoid > > > > > > > > migration issues in the future. > > > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change > from 2.11 in > > > > > > order > > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE > thinks > > > > > > this is > > > > > > > > the best course of action. > > > > > > > > > > > > > > > > Regards, > > > > > > > > -- > > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego >: > > > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > > > It contains changes we could not introduce if we release > ignite in > > > > > > its > > > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > > > olive.c...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only > blockers. I > > > > > > may be > > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego > wrote: > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because > it > > > > > contains > > > > > > > > > > > changes to code introduced by [2], which is already > included in > > > > > > > > > release. > > > > > > > > > > > > > > > > > > > > > > [1] - > https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > [2] - > https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > > > > mmu...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > The issues mentioned above were successfully > resolved and > > > > > > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for > the > > > > > delay. I > > > > > > > > think > > > > > > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > > > > > > mmu...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require > performance > > > > > > tests > > > > > > > > > rerun. > > > > > > > > > > > > > > > > > > > > > > > > > > [1] > https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > > > > [2] > https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30,
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hi, Maxim! These issues really block release. So we should wait fixes. On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > Folks, > > > I've been faced these issues, which seems to be a blocker for the > release. Please, take a look and share your thoughts. > > The server node fails when the client node with the higher java > version connects to it [1]. > The Apache Ignite build fails with missing dependency [2]. > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote: > > > > +1 > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky wrote: > > > > > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 is a > > > blocker. > > > Fix is quite easy and straightforward > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > Cherry-picked to release branch. > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov > > > > wrote: > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you cherry-pick it > > > > > to > > > > > release branch? > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > Best Regards, > > > > > > Igor > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > ilya.kasnach...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > I think it does make sense to include changes which will let us > > > > > > > avoid > > > > > > > migration issues in the future. > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change from > > > > > > > 2.11 in > > > > > order > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE > > > > > > > thinks > > > > > this is > > > > > > > the best course of action. > > > > > > > > > > > > > > Regards, > > > > > > > -- > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > It contains changes we could not introduce if we release ignite > > > > > > > > in > > > > > its > > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > > olive.c...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only > > > > > > > > > blockers. I > > > > > may be > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego > > > > > > > > > wrote: > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because it > > > > contains > > > > > > > > > > changes to code introduced by [2], which is already > > > > > > > > > > included in > > > > > > > > release. > > > > > > > > > > > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > > > mmu...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > The issues mentioned above were successfully resolved and > > > > > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the > > > > delay. I > > > > > > > think > > > > > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > > > > > mmu...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance > > > > > tests > > > > > > > > rerun. > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov < > > > > > dpav...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we > > > > > > > > > > > > > can > > > > > > > consider > > > > > > > > > both > > > > > > > > > > > as blockers. > > > > > > > > > > > > > > > > > > > > > > > > > > Just an idea to consider: >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Dmitry, We provide the source code distribution as the part of open source community. The binary distribution is an option. This means that a user MUST be able to build the binaries from the source code and currently it's not possible. So, my opinion is IGNITE-15388 is a blocker for the 2.11 release. There are few options here: - fix the version - revert the commits relates to the ignite-azure module and release them under 2.12 without a rush. The IGNITE-14725 is for discussion, I think it's better to fix it. On Fri, 27 Aug 2021 at 15:54, Dmitriy Pavlov wrote: > > What is the impact of missing artifact on our users? > > The higher java version client was never supported so I'm not really sure > we should block 2.11 because of that > > пт, 27 авг. 2021 г. в 15:51, Dmitry Pavlov : > > > Мах, the vote is about to come. > > > > So is it a sufficient reason to downvote release? > > > > Would you cast -1 for RC for that case? > > > > Sincerely, > > Dmitriy Pavlov > > > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > > Folks, > > > > > > > > > I've been faced these issues, which seems to be a blocker for the > > > release. Please, take a look and share your thoughts. > > > > > > The server node fails when the client node with the higher java > > > version connects to it [1]. > > > The Apache Ignite build fails with missing dependency [2]. > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote: > > > > > > > > +1 > > > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky > > wrote: > > > > > > > > > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 > > is a > > > > > blocker. > > > > > Fix is quite easy and straightforward > > > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > > > Best Regards, > > > > > > Igor > > > > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > > olive.c...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you > > cherry-pick it to > > > > > > > release branch? > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > > > ilya.kasnach...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > > > I think it does make sense to include changes which will let > > us avoid > > > > > > > > > migration issues in the future. > > > > > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change > > from 2.11 in > > > > > > > order > > > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE > > thinks > > > > > > > this is > > > > > > > > > the best course of action. > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > -- > > > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego > >: > > > > > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > > > > > It contains changes we could not introduce if we release > > ignite in > > > > > > > its > > > > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > > > > olive.c...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only > > blockers. I > > > > > > > may be > > > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego > > wrote: > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because > > it > > > > > > contains > > > > > > > > > > > > changes to code introduced by [2], which is already > > included in > > > > > > > > > > release. > > > > > > > > > > > > > > > > > > > > > > > > [1] - > > https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > [2] - > > https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > > > > > mmu...@apache.org> > > > > > > > > > > > wrote: > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
What is the impact of missing artifact on our users? The higher java version client was never supported so I'm not really sure we should block 2.11 because of that пт, 27 авг. 2021 г. в 15:51, Dmitry Pavlov : > Мах, the vote is about to come. > > So is it a sufficient reason to downvote release? > > Would you cast -1 for RC for that case? > > Sincerely, > Dmitriy Pavlov > > On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > > Folks, > > > > > > I've been faced these issues, which seems to be a blocker for the > > release. Please, take a look and share your thoughts. > > > > The server node fails when the client node with the higher java > > version connects to it [1]. > > The Apache Ignite build fails with missing dependency [2]. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote: > > > > > > +1 > > > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky > wrote: > > > > > > > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 > is a > > > > blocker. > > > > Fix is quite easy and straightforward > > > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > > > Cherry-picked to release branch. > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > olive.c...@gmail.com> > > > > > wrote: > > > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you > cherry-pick it to > > > > > > release branch? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > > > Best Regards, > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > > ilya.kasnach...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > > > I think it does make sense to include changes which will let > us avoid > > > > > > > > migration issues in the future. > > > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change > from 2.11 in > > > > > > order > > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE > thinks > > > > > > this is > > > > > > > > the best course of action. > > > > > > > > > > > > > > > > Regards, > > > > > > > > -- > > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego >: > > > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > > > It contains changes we could not introduce if we release > ignite in > > > > > > its > > > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > > > olive.c...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only > blockers. I > > > > > > may be > > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego > wrote: > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because > it > > > > > contains > > > > > > > > > > > changes to code introduced by [2], which is already > included in > > > > > > > > > release. > > > > > > > > > > > > > > > > > > > > > > [1] - > https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > > [2] - > https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > > > > mmu...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > The issues mentioned above were successfully > resolved and > > > > > > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for > the > > > > > delay. I > > > > > > > > think > > > > > > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > > > > > > mmu...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require > performance > > > > > > tests > > > > > > > > > rerun. > > > > > > > > > > > > > > > > > > > > > > > > > > [1] > https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > > > > [2] >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Мах, the vote is about to come. So is it a sufficient reason to downvote release? Would you cast -1 for RC for that case? Sincerely, Dmitriy Pavlov On 2021/08/27 12:46:24, Maxim Muzafarov wrote: > Folks, > > > I've been faced these issues, which seems to be a blocker for the > release. Please, take a look and share your thoughts. > > The server node fails when the client node with the higher java > version connects to it [1]. > The Apache Ignite build fails with missing dependency [2]. > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote: > > > > +1 > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky wrote: > > > > > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 is a > > > blocker. > > > Fix is quite easy and straightforward > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > Cherry-picked to release branch. > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov > > > > wrote: > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you cherry-pick it > > > > > to > > > > > release branch? > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > Best Regards, > > > > > > Igor > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > ilya.kasnach...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > I think it does make sense to include changes which will let us > > > > > > > avoid > > > > > > > migration issues in the future. > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change from > > > > > > > 2.11 in > > > > > order > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE > > > > > > > thinks > > > > > this is > > > > > > > the best course of action. > > > > > > > > > > > > > > Regards, > > > > > > > -- > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > It contains changes we could not introduce if we release ignite > > > > > > > > in > > > > > its > > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > > olive.c...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only > > > > > > > > > blockers. I > > > > > may be > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego > > > > > > > > > wrote: > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because it > > > > contains > > > > > > > > > > changes to code introduced by [2], which is already > > > > > > > > > > included in > > > > > > > > release. > > > > > > > > > > > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > > > mmu...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > The issues mentioned above were successfully resolved and > > > > > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the > > > > delay. I > > > > > > > think > > > > > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > > > > > mmu...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance > > > > > tests > > > > > > > > rerun. > > > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov < > > > > > dpav...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we > > > > > > > > > > > > > can > > > > > > > consider > > > > > > > > > both > > > > > > > > > > > as blockers. >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
I will look into 15388 On Fri, 27 Aug 2021, 18:16 Maxim Muzafarov, wrote: > Folks, > > > I've been faced these issues, which seems to be a blocker for the > release. Please, take a look and share your thoughts. > > The server node fails when the client node with the higher java > version connects to it [1]. > The Apache Ignite build fails with missing dependency [2]. > > > [1] https://issues.apache.org/jira/browse/IGNITE-14725 > [2] https://issues.apache.org/jira/browse/IGNITE-15388 > > On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote: > > > > +1 > > > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky > wrote: > > > > > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 is > a > > > blocker. > > > Fix is quite easy and straightforward > > > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > > > Cherry-picked to release branch. > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov < > olive.c...@gmail.com> > > > > wrote: > > > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you cherry-pick > it to > > > > > release branch? > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > > > I'm fine with any of these two solutions. > > > > > > > > > > > > Best Regards, > > > > > > Igor > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > > ilya.kasnach...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > I think it does make sense to include changes which will let > us avoid > > > > > > > migration issues in the future. > > > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change from > 2.11 in > > > > > order > > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE > thinks > > > > > this is > > > > > > > the best course of action. > > > > > > > > > > > > > > Regards, > > > > > > > -- > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > > > It contains changes we could not introduce if we release > ignite in > > > > > its > > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > > olive.c...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only > blockers. I > > > > > may be > > > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego > wrote: > > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because it > > > > contains > > > > > > > > > > changes to code introduced by [2], which is already > included in > > > > > > > > release. > > > > > > > > > > > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > > > mmu...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > The issues mentioned above were successfully resolved > and > > > > > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the > > > > delay. I > > > > > > > think > > > > > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > > > > > mmu...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require > performance > > > > > tests > > > > > > > > rerun. > > > > > > > > > > > > > > > > > > > > > > > > [1] > https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > > > [2] > https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov < > > > > > dpav...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, > we can > > > > > > > consider > > > > > > > > > both > > > > > > > > > > > as blockers. > > > > > > > > > > > > > > > > > > > > > > > > > > Just an idea to consider: > > > > > > > > > > > > > For fixed ticket/PR ( > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-15170) > most > > > > > likely > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, I've been faced these issues, which seems to be a blocker for the release. Please, take a look and share your thoughts. The server node fails when the client node with the higher java version connects to it [1]. The Apache Ignite build fails with missing dependency [2]. [1] https://issues.apache.org/jira/browse/IGNITE-14725 [2] https://issues.apache.org/jira/browse/IGNITE-15388 On Mon, 9 Aug 2021 at 16:56, Maxim Muzafarov wrote: > > +1 > > On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky wrote: > > > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 is a > > blocker. > > Fix is quite easy and straightforward > > > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > > > Cherry-picked to release branch. > > > > > > Best Regards, > > > Igor > > > > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov > > > wrote: > > > > > > > Ok, I think we should add [1] to 2.11 release. Can you cherry-pick it to > > > > release branch? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > > I'm fine with any of these two solutions. > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > > ilya.kasnach...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hello! > > > > > > > > > > > > I think it does make sense to include changes which will let us > > > > > > avoid > > > > > > migration issues in the future. > > > > > > > > > > > > Alternatively, maybe we can revert the incomplete change from 2.11 > > > > > > in > > > > order > > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE thinks > > > > this is > > > > > > the best course of action. > > > > > > > > > > > > Regards, > > > > > > -- > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > > > > > > > > > > > Alexey, > > > > > > > > > > > > > > It contains changes we could not introduce if we release ignite in > > > > its > > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > > > Best Regards, > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > > olive.c...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only blockers. I > > > > may be > > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > > > > > > > > Igniters, > > > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because it > > > contains > > > > > > > > > changes to code introduced by [2], which is already included > > > > > > > > > in > > > > > > > release. > > > > > > > > > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > > mmu...@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > The issues mentioned above were successfully resolved and > > > > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the > > > delay. I > > > > > > think > > > > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > > > > mmu...@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance > > > > tests > > > > > > > rerun. > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov < > > > > dpav...@apache.org> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can > > > > > > consider > > > > > > > > both > > > > > > > > > > as blockers. > > > > > > > > > > > > > > > > > > > > > > > > Just an idea to consider: > > > > > > > > > > > > For fixed ticket/PR ( > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-15170) most > > > > likely > > > > > > we > > > > > > > > don't > > > > > > > > > > need to re-run performance tests. > > > > > > > > > > > > > > > > > > > > > > > > If second issue has no impact on performance, we can > > > > > > > > > > > > take > > > > perf > > > > > > > > results > > > > > > > > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > > > > > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
+1 On Mon, 9 Aug 2021 at 16:27, Ivan Daschinsky wrote: > > I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 is a > blocker. > Fix is quite easy and straightforward > > пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > > > Cherry-picked to release branch. > > > > Best Regards, > > Igor > > > > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov > > wrote: > > > > > Ok, I think we should add [1] to 2.11 release. Can you cherry-pick it to > > > release branch? > > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > > I'm fine with any of these two solutions. > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > > ilya.kasnach...@gmail.com> > > > > wrote: > > > > > > > > > Hello! > > > > > > > > > > I think it does make sense to include changes which will let us avoid > > > > > migration issues in the future. > > > > > > > > > > Alternatively, maybe we can revert the incomplete change from 2.11 in > > > order > > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE thinks > > > this is > > > > > the best course of action. > > > > > > > > > > Regards, > > > > > -- > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > > > > > > > > > Alexey, > > > > > > > > > > > > It contains changes we could not introduce if we release ignite in > > > its > > > > > > current state as they are going to be breaking changes. > > > > > > > > > > > > Best Regards, > > > > > > Igor > > > > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > > olive.c...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > > > Now we are in stabilization phase and accepting only blockers. I > > > may be > > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > > > > > > > Igniters, > > > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because it > > contains > > > > > > > > changes to code introduced by [2], which is already included in > > > > > > release. > > > > > > > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > > mmu...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > The issues mentioned above were successfully resolved and > > > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the > > delay. I > > > > > think > > > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > > > mmu...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance > > > tests > > > > > > rerun. > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov < > > > dpav...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can > > > > > consider > > > > > > > both > > > > > > > > > as blockers. > > > > > > > > > > > > > > > > > > > > > > Just an idea to consider: > > > > > > > > > > > For fixed ticket/PR ( > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-15170) most > > > likely > > > > > we > > > > > > > don't > > > > > > > > > need to re-run performance tests. > > > > > > > > > > > > > > > > > > > > > > If second issue has no impact on performance, we can take > > > perf > > > > > > > results > > > > > > > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > > > > > > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" < > > > nizhi...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > +1 to fix both prior to release > > > > > > > > > > > > > > > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > > > > > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov < > > > > > mmu...@apache.org > > > > > > > > > > > > > > > > написал(а): > > > > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > > > We've faced [1][2] issues related to the new > > > functionality > > > > > > > added to > > > > > > > > > > > > > the 2.11 release (it will be safe to merge to the > > > release > > > > > > > branch). > > > > > > > > > > > > > From my point of view, both of them are critical and > > > must >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 is a blocker. Fix is quite easy and straightforward пн, 2 авг. 2021 г. в 03:11, Igor Sapego : > Cherry-picked to release branch. > > Best Regards, > Igor > > > On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov > wrote: > > > Ok, I think we should add [1] to 2.11 release. Can you cherry-pick it to > > release branch? > > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > > I'm fine with any of these two solutions. > > > > > > Best Regards, > > > Igor > > > > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > > ilya.kasnach...@gmail.com> > > > wrote: > > > > > > > Hello! > > > > > > > > I think it does make sense to include changes which will let us avoid > > > > migration issues in the future. > > > > > > > > Alternatively, maybe we can revert the incomplete change from 2.11 in > > order > > > > to reintroduce it in 2.12 in full form if Igor agrees and RE thinks > > this is > > > > the best course of action. > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > > > > > > > Alexey, > > > > > > > > > > It contains changes we could not introduce if we release ignite in > > its > > > > > current state as they are going to be breaking changes. > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > > olive.c...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi, Igor! > > > > > > > > > > > > Now we are in stabilization phase and accepting only blockers. I > > may be > > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > > > > > > Igniters, > > > > > > > > > > > > > > I suggest adding [1] to the scope of release, because it > contains > > > > > > > changes to code introduced by [2], which is already included in > > > > > release. > > > > > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > > > Best Regards, > > > > > > > Igor > > > > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > > mmu...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > The issues mentioned above were successfully resolved and > > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the > delay. I > > > > think > > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > > mmu...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance > > tests > > > > > rerun. > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov < > > dpav...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can > > > > consider > > > > > > both > > > > > > > > as blockers. > > > > > > > > > > > > > > > > > > > > Just an idea to consider: > > > > > > > > > > For fixed ticket/PR ( > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-15170) most > > likely > > > > we > > > > > > don't > > > > > > > > need to re-run performance tests. > > > > > > > > > > > > > > > > > > > > If second issue has no impact on performance, we can take > > perf > > > > > > results > > > > > > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > > > > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" < > > nizhi...@apache.org> > > > > > > wrote: > > > > > > > > > > > +1 to fix both prior to release > > > > > > > > > > > > > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > > > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov < > > > > mmu...@apache.org > > > > > > > > > > > > > > написал(а): > > > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > > > We've faced [1][2] issues related to the new > > functionality > > > > > > added to > > > > > > > > > > > > the 2.11 release (it will be safe to merge to the > > release > > > > > > branch). > > > > > > > > > > > > From my point of view, both of them are critical and > > must > > > > be > > > > > > > > included > > > > > > > > > > > > in the 2.11 release. > > > > > > > > > > > > The [2] is ready for merge. The [1] will be completed > > by > > > > the > > > > > > end > > > > > > > > of this week. > > > > > > > > > > > > > > > > > > > > > > > > Please share your thoughts. > > > > > > > > > > > > > > > > > > > > > > > > [1] >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Cherry-picked to release branch. Best Regards, Igor On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov wrote: > Ok, I think we should add [1] to 2.11 release. Can you cherry-pick it to > release branch? > [1] https://issues.apache.org/jira/browse/IGNITE-14815 > > On 2021/07/30 02:25:25, Igor Sapego wrote: > > I'm fine with any of these two solutions. > > > > Best Regards, > > Igor > > > > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> > > wrote: > > > > > Hello! > > > > > > I think it does make sense to include changes which will let us avoid > > > migration issues in the future. > > > > > > Alternatively, maybe we can revert the incomplete change from 2.11 in > order > > > to reintroduce it in 2.12 in full form if Igor agrees and RE thinks > this is > > > the best course of action. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > > > > > Alexey, > > > > > > > > It contains changes we could not introduce if we release ignite in > its > > > > current state as they are going to be breaking changes. > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov < > olive.c...@gmail.com> > > > > wrote: > > > > > > > > > Hi, Igor! > > > > > > > > > > Now we are in stabilization phase and accepting only blockers. I > may be > > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > > > > > Igniters, > > > > > > > > > > > > I suggest adding [1] to the scope of release, because it contains > > > > > > changes to code introduced by [2], which is already included in > > > > release. > > > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > > > Best Regards, > > > > > > Igor > > > > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov < > mmu...@apache.org> > > > > > wrote: > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > The issues mentioned above were successfully resolved and > > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the delay. I > > > think > > > > > > > we can proceed with the release. > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov < > mmu...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance > tests > > > > rerun. > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov < > dpav...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can > > > consider > > > > > both > > > > > > > as blockers. > > > > > > > > > > > > > > > > > > Just an idea to consider: > > > > > > > > > For fixed ticket/PR ( > > > > > > > https://issues.apache.org/jira/browse/IGNITE-15170) most > likely > > > we > > > > > don't > > > > > > > need to re-run performance tests. > > > > > > > > > > > > > > > > > > If second issue has no impact on performance, we can take > perf > > > > > results > > > > > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" < > nizhi...@apache.org> > > > > > wrote: > > > > > > > > > > +1 to fix both prior to release > > > > > > > > > > > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov < > > > mmu...@apache.org > > > > > > > > > > > > написал(а): > > > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > > > We've faced [1][2] issues related to the new > functionality > > > > > added to > > > > > > > > > > > the 2.11 release (it will be safe to merge to the > release > > > > > branch). > > > > > > > > > > > From my point of view, both of them are critical and > must > > > be > > > > > > > included > > > > > > > > > > > in the 2.11 release. > > > > > > > > > > > The [2] is ready for merge. The [1] will be completed > by > > > the > > > > > end > > > > > > > of this week. > > > > > > > > > > > > > > > > > > > > > > Please share your thoughts. > > > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov < > > > > > mmu...@apache.org> > > > > > > > wrote: > > > > > > > > > > >> > > > > > > > > > > >> Folks, > > > > > > > > > > >> > > > > > > > > > > >> Since the release branch was created some time ago, > should > > > > we > > > > > > > bump up > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Ok, I think we should add [1] to 2.11 release. Can you cherry-pick it to release branch? [1] https://issues.apache.org/jira/browse/IGNITE-14815 On 2021/07/30 02:25:25, Igor Sapego wrote: > I'm fine with any of these two solutions. > > Best Regards, > Igor > > > On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev > wrote: > > > Hello! > > > > I think it does make sense to include changes which will let us avoid > > migration issues in the future. > > > > Alternatively, maybe we can revert the incomplete change from 2.11 in order > > to reintroduce it in 2.12 in full form if Igor agrees and RE thinks this is > > the best course of action. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > > > Alexey, > > > > > > It contains changes we could not introduce if we release ignite in its > > > current state as they are going to be breaking changes. > > > > > > Best Regards, > > > Igor > > > > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov > > > wrote: > > > > > > > Hi, Igor! > > > > > > > > Now we are in stabilization phase and accepting only blockers. I may be > > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > > > > Igniters, > > > > > > > > > > I suggest adding [1] to the scope of release, because it contains > > > > > changes to code introduced by [2], which is already included in > > > release. > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov > > > > wrote: > > > > > > > > > > > Folks, > > > > > > > > > > > > The issues mentioned above were successfully resolved and > > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the delay. I > > think > > > > > > we can proceed with the release. > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov > > > > wrote: > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance tests > > > rerun. > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov > > > > wrote: > > > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can > > consider > > > > both > > > > > > as blockers. > > > > > > > > > > > > > > > > Just an idea to consider: > > > > > > > > For fixed ticket/PR ( > > > > > > https://issues.apache.org/jira/browse/IGNITE-15170) most likely > > we > > > > don't > > > > > > need to re-run performance tests. > > > > > > > > > > > > > > > > If second issue has no impact on performance, we can take perf > > > > results > > > > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" > > > > wrote: > > > > > > > > > +1 to fix both prior to release > > > > > > > > > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov < > > mmu...@apache.org > > > > > > > > > > написал(а): > > > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > > > We've faced [1][2] issues related to the new functionality > > > > added to > > > > > > > > > > the 2.11 release (it will be safe to merge to the release > > > > branch). > > > > > > > > > > From my point of view, both of them are critical and must > > be > > > > > > included > > > > > > > > > > in the 2.11 release. > > > > > > > > > > The [2] is ready for merge. The [1] will be completed by > > the > > > > end > > > > > > of this week. > > > > > > > > > > > > > > > > > > > > Please share your thoughts. > > > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov < > > > > mmu...@apache.org> > > > > > > wrote: > > > > > > > > > >> > > > > > > > > > >> Folks, > > > > > > > > > >> > > > > > > > > > >> Since the release branch was created some time ago, should > > > we > > > > > > bump up > > > > > > > > > >> the master branch version to the next one? > > > > > > > > > >> > > > > > > > > > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov < > > > > > > olive.c...@gmail.com> wrote: > > > > > > > > > >>> > > > > > > > > > >>> Hi, Pavel. > > > > > > > > > >>> > > > > > > > > > >>> I think, it looks like blocker. Please cherry-pick it to > > > 2.11 > > > > > > release branch > > > > > > > > > >>> > > > > > > > > > >>> On 2021/07/01 09:29:57, Pavel Pereslegin < > > xxt...@gmail.com > > > > > > > > > > wrote: > > > > > > > > > Hello, Alexey! > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
I'm fine with any of these two solutions. Best Regards, Igor On Thu, Jul 29, 2021 at 6:36 PM Ilya Kasnacheev wrote: > Hello! > > I think it does make sense to include changes which will let us avoid > migration issues in the future. > > Alternatively, maybe we can revert the incomplete change from 2.11 in order > to reintroduce it in 2.12 in full form if Igor agrees and RE thinks this is > the best course of action. > > Regards, > -- > Ilya Kasnacheev > > > чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > > > Alexey, > > > > It contains changes we could not introduce if we release ignite in its > > current state as they are going to be breaking changes. > > > > Best Regards, > > Igor > > > > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov > > wrote: > > > > > Hi, Igor! > > > > > > Now we are in stabilization phase and accepting only blockers. I may be > > > wrong, but this ticket doesn't seem to be of that kind. > > > > > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > > > Igniters, > > > > > > > > I suggest adding [1] to the scope of release, because it contains > > > > changes to code introduced by [2], which is already included in > > release. > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov > > > wrote: > > > > > > > > > Folks, > > > > > > > > > > The issues mentioned above were successfully resolved and > > > > > cherry-picked to the ignite-2.11 branch. Sorry for the delay. I > think > > > > > we can proceed with the release. > > > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov > > > wrote: > > > > > > > > > > > > Folks, > > > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance tests > > rerun. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov > > > wrote: > > > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can > consider > > > both > > > > > as blockers. > > > > > > > > > > > > > > Just an idea to consider: > > > > > > > For fixed ticket/PR ( > > > > > https://issues.apache.org/jira/browse/IGNITE-15170) most likely > we > > > don't > > > > > need to re-run performance tests. > > > > > > > > > > > > > > If second issue has no impact on performance, we can take perf > > > results > > > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" > > > wrote: > > > > > > > > +1 to fix both prior to release > > > > > > > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov < > mmu...@apache.org > > > > > > > > написал(а): > > > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > We've faced [1][2] issues related to the new functionality > > > added to > > > > > > > > > the 2.11 release (it will be safe to merge to the release > > > branch). > > > > > > > > > From my point of view, both of them are critical and must > be > > > > > included > > > > > > > > > in the 2.11 release. > > > > > > > > > The [2] is ready for merge. The [1] will be completed by > the > > > end > > > > > of this week. > > > > > > > > > > > > > > > > > > Please share your thoughts. > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov < > > > mmu...@apache.org> > > > > > wrote: > > > > > > > > >> > > > > > > > > >> Folks, > > > > > > > > >> > > > > > > > > >> Since the release branch was created some time ago, should > > we > > > > > bump up > > > > > > > > >> the master branch version to the next one? > > > > > > > > >> > > > > > > > > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov < > > > > > olive.c...@gmail.com> wrote: > > > > > > > > >>> > > > > > > > > >>> Hi, Pavel. > > > > > > > > >>> > > > > > > > > >>> I think, it looks like blocker. Please cherry-pick it to > > 2.11 > > > > > release branch > > > > > > > > >>> > > > > > > > > >>> On 2021/07/01 09:29:57, Pavel Pereslegin < > xxt...@gmail.com > > > > > > > > wrote: > > > > > > > > Hello, Alexey! > > > > > > > > > > > > > > > > Is it possible to include a hotfix that corrects the > > command > > > > > syntax > > > > > > > > output in the control script? [1] > > > > > > > > > > > > > > > > This bug can significantly complicate the use of the > > > snapshot > > > > > restore > > > > > > > > function (one of the important features of 2.11). In > > > addition, > > > > > this > > > > > > > > may raise a number of questions to the product support, > > > which > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hello! I think it does make sense to include changes which will let us avoid migration issues in the future. Alternatively, maybe we can revert the incomplete change from 2.11 in order to reintroduce it in 2.12 in full form if Igor agrees and RE thinks this is the best course of action. Regards, -- Ilya Kasnacheev чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > Alexey, > > It contains changes we could not introduce if we release ignite in its > current state as they are going to be breaking changes. > > Best Regards, > Igor > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov > wrote: > > > Hi, Igor! > > > > Now we are in stabilization phase and accepting only blockers. I may be > > wrong, but this ticket doesn't seem to be of that kind. > > > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > > Igniters, > > > > > > I suggest adding [1] to the scope of release, because it contains > > > changes to code introduced by [2], which is already included in > release. > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > Best Regards, > > > Igor > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov > > wrote: > > > > > > > Folks, > > > > > > > > The issues mentioned above were successfully resolved and > > > > cherry-picked to the ignite-2.11 branch. Sorry for the delay. I think > > > > we can proceed with the release. > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov > > wrote: > > > > > > > > > > Folks, > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance tests > rerun. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov > > wrote: > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can consider > > both > > > > as blockers. > > > > > > > > > > > > Just an idea to consider: > > > > > > For fixed ticket/PR ( > > > > https://issues.apache.org/jira/browse/IGNITE-15170) most likely we > > don't > > > > need to re-run performance tests. > > > > > > > > > > > > If second issue has no impact on performance, we can take perf > > results > > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" > > wrote: > > > > > > > +1 to fix both prior to release > > > > > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov > > > > > написал(а): > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > We've faced [1][2] issues related to the new functionality > > added to > > > > > > > > the 2.11 release (it will be safe to merge to the release > > branch). > > > > > > > > From my point of view, both of them are critical and must be > > > > included > > > > > > > > in the 2.11 release. > > > > > > > > The [2] is ready for merge. The [1] will be completed by the > > end > > > > of this week. > > > > > > > > > > > > > > > > Please share your thoughts. > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov < > > mmu...@apache.org> > > > > wrote: > > > > > > > >> > > > > > > > >> Folks, > > > > > > > >> > > > > > > > >> Since the release branch was created some time ago, should > we > > > > bump up > > > > > > > >> the master branch version to the next one? > > > > > > > >> > > > > > > > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov < > > > > olive.c...@gmail.com> wrote: > > > > > > > >>> > > > > > > > >>> Hi, Pavel. > > > > > > > >>> > > > > > > > >>> I think, it looks like blocker. Please cherry-pick it to > 2.11 > > > > release branch > > > > > > > >>> > > > > > > > >>> On 2021/07/01 09:29:57, Pavel Pereslegin > > > > > wrote: > > > > > > > Hello, Alexey! > > > > > > > > > > > > > > Is it possible to include a hotfix that corrects the > command > > > > syntax > > > > > > > output in the control script? [1] > > > > > > > > > > > > > > This bug can significantly complicate the use of the > > snapshot > > > > restore > > > > > > > function (one of the important features of 2.11). In > > addition, > > > > this > > > > > > > may raise a number of questions to the product support, > > which > > > > we can > > > > > > > prevent by adding this patch in 2.11. > > > > > > > > > > > > > > This patch does not affect any functions other than the > > "help" > > > > output > > > > > > > of the control script. > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > > > > > > > > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov < > > > > olive.c...@gmail.com>: > > > > > > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Alexey, It contains changes we could not introduce if we release ignite in its current state as they are going to be breaking changes. Best Regards, Igor On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov wrote: > Hi, Igor! > > Now we are in stabilization phase and accepting only blockers. I may be > wrong, but this ticket doesn't seem to be of that kind. > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > Igniters, > > > > I suggest adding [1] to the scope of release, because it contains > > changes to code introduced by [2], which is already included in release. > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > Best Regards, > > Igor > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov > wrote: > > > > > Folks, > > > > > > The issues mentioned above were successfully resolved and > > > cherry-picked to the ignite-2.11 branch. Sorry for the delay. I think > > > we can proceed with the release. > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov > wrote: > > > > > > > > Folks, > > > > > > > > Yes, both the fixes [1] [2] will not require performance tests rerun. > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov > wrote: > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can consider > both > > > as blockers. > > > > > > > > > > Just an idea to consider: > > > > > For fixed ticket/PR ( > > > https://issues.apache.org/jira/browse/IGNITE-15170) most likely we > don't > > > need to re-run performance tests. > > > > > > > > > > If second issue has no impact on performance, we can take perf > results > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" > wrote: > > > > > > +1 to fix both prior to release > > > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov > > > написал(а): > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > We've faced [1][2] issues related to the new functionality > added to > > > > > > > the 2.11 release (it will be safe to merge to the release > branch). > > > > > > > From my point of view, both of them are critical and must be > > > included > > > > > > > in the 2.11 release. > > > > > > > The [2] is ready for merge. The [1] will be completed by the > end > > > of this week. > > > > > > > > > > > > > > Please share your thoughts. > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov < > mmu...@apache.org> > > > wrote: > > > > > > >> > > > > > > >> Folks, > > > > > > >> > > > > > > >> Since the release branch was created some time ago, should we > > > bump up > > > > > > >> the master branch version to the next one? > > > > > > >> > > > > > > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov < > > > olive.c...@gmail.com> wrote: > > > > > > >>> > > > > > > >>> Hi, Pavel. > > > > > > >>> > > > > > > >>> I think, it looks like blocker. Please cherry-pick it to 2.11 > > > release branch > > > > > > >>> > > > > > > >>> On 2021/07/01 09:29:57, Pavel Pereslegin > > > wrote: > > > > > > Hello, Alexey! > > > > > > > > > > > > Is it possible to include a hotfix that corrects the command > > > syntax > > > > > > output in the control script? [1] > > > > > > > > > > > > This bug can significantly complicate the use of the > snapshot > > > restore > > > > > > function (one of the important features of 2.11). In > addition, > > > this > > > > > > may raise a number of questions to the product support, > which > > > we can > > > > > > prevent by adding this patch in 2.11. > > > > > > > > > > > > This patch does not affect any functions other than the > "help" > > > output > > > > > > of the control script. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > > > > > > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov < > > > olive.c...@gmail.com>: > > > > > > > > > > > > > > Hi, Iilya! > > > > > > > > > > > > > > As I can see, this feature highly improves debugging during > > > incidents. So I think we can call it blocker and cherry-pick to > ignite-2.11 > > > branch > > > > > > > > > > > > > > On 2021/06/30 20:26:43, Shishkov Ilya < > shishkovi...@gmail.com> > > > wrote: > > > > > > >> Hello, Alexey! > > > > > > >> Is it possible to add system views for BaselineNode > > > attributes [1] and > > > > > > >> corresponding documentation [2] to 2.11? > > > > > > >> > > > > > > >> 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > > > > > >> 2.
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hi, Igor! Now we are in stabilization phase and accepting only blockers. I may be wrong, but this ticket doesn't seem to be of that kind. On 2021/07/28 21:00:15, Igor Sapego wrote: > Igniters, > > I suggest adding [1] to the scope of release, because it contains > changes to code introduced by [2], which is already included in release. > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > Best Regards, > Igor > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov wrote: > > > Folks, > > > > The issues mentioned above were successfully resolved and > > cherry-picked to the ignite-2.11 branch. Sorry for the delay. I think > > we can proceed with the release. > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov wrote: > > > > > > Folks, > > > > > > Yes, both the fixes [1] [2] will not require performance tests rerun. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov wrote: > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can consider both > > as blockers. > > > > > > > > Just an idea to consider: > > > > For fixed ticket/PR ( > > https://issues.apache.org/jira/browse/IGNITE-15170) most likely we don't > > need to re-run performance tests. > > > > > > > > If second issue has no impact on performance, we can take perf results > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" wrote: > > > > > +1 to fix both prior to release > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov > > написал(а): > > > > > > > > > > > > Folks, > > > > > > > > > > > > We've faced [1][2] issues related to the new functionality added to > > > > > > the 2.11 release (it will be safe to merge to the release branch). > > > > > > From my point of view, both of them are critical and must be > > included > > > > > > in the 2.11 release. > > > > > > The [2] is ready for merge. The [1] will be completed by the end > > of this week. > > > > > > > > > > > > Please share your thoughts. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov > > wrote: > > > > > >> > > > > > >> Folks, > > > > > >> > > > > > >> Since the release branch was created some time ago, should we > > bump up > > > > > >> the master branch version to the next one? > > > > > >> > > > > > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov < > > olive.c...@gmail.com> wrote: > > > > > >>> > > > > > >>> Hi, Pavel. > > > > > >>> > > > > > >>> I think, it looks like blocker. Please cherry-pick it to 2.11 > > release branch > > > > > >>> > > > > > >>> On 2021/07/01 09:29:57, Pavel Pereslegin > > wrote: > > > > > Hello, Alexey! > > > > > > > > > > Is it possible to include a hotfix that corrects the command > > syntax > > > > > output in the control script? [1] > > > > > > > > > > This bug can significantly complicate the use of the snapshot > > restore > > > > > function (one of the important features of 2.11). In addition, > > this > > > > > may raise a number of questions to the product support, which > > we can > > > > > prevent by adding this patch in 2.11. > > > > > > > > > > This patch does not affect any functions other than the "help" > > output > > > > > of the control script. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > > > > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov < > > olive.c...@gmail.com>: > > > > > > > > > > > > Hi, Iilya! > > > > > > > > > > > > As I can see, this feature highly improves debugging during > > incidents. So I think we can call it blocker and cherry-pick to ignite-2.11 > > branch > > > > > > > > > > > > On 2021/06/30 20:26:43, Shishkov Ilya > > wrote: > > > > > >> Hello, Alexey! > > > > > >> Is it possible to add system views for BaselineNode > > attributes [1] and > > > > > >> corresponding documentation [2] to 2.11? > > > > > >> > > > > > >> 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > > > > >> 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > > > > >> > > > > > >> ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev < > > namelc...@apache.org>: > > > > > >> > > > > > >>> Thanks! I have cherry-picked the commit to the 2.11 branch. > > > > > >>> > > > > > >>> ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov < > > olive.c...@gmail.com>: > > > > > > > > > > Hi, Nikita! > > > > > > > > > > I think it's important fix and should be included in 2.11 > > release. I've > > > > > >>> tagged ticket by
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Igniters, I suggest adding [1] to the scope of release, because it contains changes to code introduced by [2], which is already included in release. [1] - https://issues.apache.org/jira/browse/IGNITE-14815 [2] - https://issues.apache.org/jira/browse/IGNITE-14658 Best Regards, Igor On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov wrote: > Folks, > > The issues mentioned above were successfully resolved and > cherry-picked to the ignite-2.11 branch. Sorry for the delay. I think > we can proceed with the release. > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov wrote: > > > > Folks, > > > > Yes, both the fixes [1] [2] will not require performance tests rerun. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov wrote: > > > > > > I personally trust opinion of Nikolay and Maxim, we can consider both > as blockers. > > > > > > Just an idea to consider: > > > For fixed ticket/PR ( > https://issues.apache.org/jira/browse/IGNITE-15170) most likely we don't > need to re-run performance tests. > > > > > > If second issue has no impact on performance, we can take perf results > from rc.-1 and run only functional tests for rc.0. > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" wrote: > > > > +1 to fix both prior to release > > > > > > > > Отправлено с iPhone > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov > написал(а): > > > > > > > > > > Folks, > > > > > > > > > > We've faced [1][2] issues related to the new functionality added to > > > > > the 2.11 release (it will be safe to merge to the release branch). > > > > > From my point of view, both of them are critical and must be > included > > > > > in the 2.11 release. > > > > > The [2] is ready for merge. The [1] will be completed by the end > of this week. > > > > > > > > > > Please share your thoughts. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov > wrote: > > > > >> > > > > >> Folks, > > > > >> > > > > >> Since the release branch was created some time ago, should we > bump up > > > > >> the master branch version to the next one? > > > > >> > > > > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov < > olive.c...@gmail.com> wrote: > > > > >>> > > > > >>> Hi, Pavel. > > > > >>> > > > > >>> I think, it looks like blocker. Please cherry-pick it to 2.11 > release branch > > > > >>> > > > > >>> On 2021/07/01 09:29:57, Pavel Pereslegin > wrote: > > > > Hello, Alexey! > > > > > > > > Is it possible to include a hotfix that corrects the command > syntax > > > > output in the control script? [1] > > > > > > > > This bug can significantly complicate the use of the snapshot > restore > > > > function (one of the important features of 2.11). In addition, > this > > > > may raise a number of questions to the product support, which > we can > > > > prevent by adding this patch in 2.11. > > > > > > > > This patch does not affect any functions other than the "help" > output > > > > of the control script. > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov < > olive.c...@gmail.com>: > > > > > > > > > > Hi, Iilya! > > > > > > > > > > As I can see, this feature highly improves debugging during > incidents. So I think we can call it blocker and cherry-pick to ignite-2.11 > branch > > > > > > > > > > On 2021/06/30 20:26:43, Shishkov Ilya > wrote: > > > > >> Hello, Alexey! > > > > >> Is it possible to add system views for BaselineNode > attributes [1] and > > > > >> corresponding documentation [2] to 2.11? > > > > >> > > > > >> 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > > > >> 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > > > >> > > > > >> ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev < > namelc...@apache.org>: > > > > >> > > > > >>> Thanks! I have cherry-picked the commit to the 2.11 branch. > > > > >>> > > > > >>> ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov < > olive.c...@gmail.com>: > > > > > > > > Hi, Nikita! > > > > > > > > I think it's important fix and should be included in 2.11 > release. I've > > > > >>> tagged ticket by fixVersion 2.11. Can you cherry-pick it to > ignite-2.11 > > > > >>> branch? And please fill release notes or delete flag. > > > > > > > > On 2021/06/30 07:55:04, Nikita Amelchev < > namelc...@apache.org> wrote: > > > > > Hello, Alexey. > > > > > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. > It fixes > > > > > incorrect values of cache, cache groups, data region > metrics after > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, The issues mentioned above were successfully resolved and cherry-picked to the ignite-2.11 branch. Sorry for the delay. I think we can proceed with the release. On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov wrote: > > Folks, > > Yes, both the fixes [1] [2] will not require performance tests rerun. > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov wrote: > > > > I personally trust opinion of Nikolay and Maxim, we can consider both as > > blockers. > > > > Just an idea to consider: > > For fixed ticket/PR (https://issues.apache.org/jira/browse/IGNITE-15170) > > most likely we don't need to re-run performance tests. > > > > If second issue has no impact on performance, we can take perf results from > > rc.-1 and run only functional tests for rc.0. > > > > On 2021/07/22 04:44:01, "Николай Ижиков" wrote: > > > +1 to fix both prior to release > > > > > > Отправлено с iPhone > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov > > > > написал(а): > > > > > > > > Folks, > > > > > > > > We've faced [1][2] issues related to the new functionality added to > > > > the 2.11 release (it will be safe to merge to the release branch). > > > > From my point of view, both of them are critical and must be included > > > > in the 2.11 release. > > > > The [2] is ready for merge. The [1] will be completed by the end of > > > > this week. > > > > > > > > Please share your thoughts. > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov > > > >> wrote: > > > >> > > > >> Folks, > > > >> > > > >> Since the release branch was created some time ago, should we bump up > > > >> the master branch version to the next one? > > > >> > > > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov > > > >>> wrote: > > > >>> > > > >>> Hi, Pavel. > > > >>> > > > >>> I think, it looks like blocker. Please cherry-pick it to 2.11 release > > > >>> branch > > > >>> > > > >>> On 2021/07/01 09:29:57, Pavel Pereslegin wrote: > > > Hello, Alexey! > > > > > > Is it possible to include a hotfix that corrects the command syntax > > > output in the control script? [1] > > > > > > This bug can significantly complicate the use of the snapshot restore > > > function (one of the important features of 2.11). In addition, this > > > may raise a number of questions to the product support, which we can > > > prevent by adding this patch in 2.11. > > > > > > This patch does not affect any functions other than the "help" output > > > of the control script. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > > > > > > > Hi, Iilya! > > > > > > > > As I can see, this feature highly improves debugging during > > > > incidents. So I think we can call it blocker and cherry-pick to > > > > ignite-2.11 branch > > > > > > > > On 2021/06/30 20:26:43, Shishkov Ilya > > > > wrote: > > > >> Hello, Alexey! > > > >> Is it possible to add system views for BaselineNode attributes [1] > > > >> and > > > >> corresponding documentation [2] to 2.11? > > > >> > > > >> 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > > >> 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > > >> > > > >> ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev > > > >> : > > > >> > > > >>> Thanks! I have cherry-picked the commit to the 2.11 branch. > > > >>> > > > >>> ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov > > > >>> : > > > > > > Hi, Nikita! > > > > > > I think it's important fix and should be included in 2.11 > > > release. I've > > > >>> tagged ticket by fixVersion 2.11. Can you cherry-pick it to > > > >>> ignite-2.11 > > > >>> branch? And please fill release notes or delete flag. > > > > > > On 2021/06/30 07:55:04, Nikita Amelchev > > > wrote: > > > > Hello, Alexey. > > > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It > > > > fixes > > > > incorrect values of cache, cache groups, data region metrics > > > > after > > > > cluster reactivation. > > > > WDYT? > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov > > > > : > > > >> > > > >> Ok, we can add this fix to release scope. > > > >> > > > >> On 2021/06/29 08:36:00, Сурков Александр > > > >>> Викторович wrote: > > > >>> Hi Alexey. > > > >>> > > > >>> I think need
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, Yes, both the fixes [1] [2] will not require performance tests rerun. [1] https://issues.apache.org/jira/browse/IGNITE-15146 [2] https://issues.apache.org/jira/browse/IGNITE-15170 On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov wrote: > > I personally trust opinion of Nikolay and Maxim, we can consider both as > blockers. > > Just an idea to consider: > For fixed ticket/PR (https://issues.apache.org/jira/browse/IGNITE-15170) > most likely we don't need to re-run performance tests. > > If second issue has no impact on performance, we can take perf results from > rc.-1 and run only functional tests for rc.0. > > On 2021/07/22 04:44:01, "Николай Ижиков" wrote: > > +1 to fix both prior to release > > > > Отправлено с iPhone > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov написал(а): > > > > > > Folks, > > > > > > We've faced [1][2] issues related to the new functionality added to > > > the 2.11 release (it will be safe to merge to the release branch). > > > From my point of view, both of them are critical and must be included > > > in the 2.11 release. > > > The [2] is ready for merge. The [1] will be completed by the end of this > > > week. > > > > > > Please share your thoughts. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov wrote: > > >> > > >> Folks, > > >> > > >> Since the release branch was created some time ago, should we bump up > > >> the master branch version to the next one? > > >> > > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov > > >>> wrote: > > >>> > > >>> Hi, Pavel. > > >>> > > >>> I think, it looks like blocker. Please cherry-pick it to 2.11 release > > >>> branch > > >>> > > >>> On 2021/07/01 09:29:57, Pavel Pereslegin wrote: > > Hello, Alexey! > > > > Is it possible to include a hotfix that corrects the command syntax > > output in the control script? [1] > > > > This bug can significantly complicate the use of the snapshot restore > > function (one of the important features of 2.11). In addition, this > > may raise a number of questions to the product support, which we can > > prevent by adding this patch in 2.11. > > > > This patch does not affect any functions other than the "help" output > > of the control script. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > > > > > Hi, Iilya! > > > > > > As I can see, this feature highly improves debugging during > > > incidents. So I think we can call it blocker and cherry-pick to > > > ignite-2.11 branch > > > > > > On 2021/06/30 20:26:43, Shishkov Ilya wrote: > > >> Hello, Alexey! > > >> Is it possible to add system views for BaselineNode attributes [1] > > >> and > > >> corresponding documentation [2] to 2.11? > > >> > > >> 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > >> 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > >> > > >> ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > > >> > > >>> Thanks! I have cherry-picked the commit to the 2.11 branch. > > >>> > > >>> ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > > > Hi, Nikita! > > > > I think it's important fix and should be included in 2.11 release. > > I've > > >>> tagged ticket by fixVersion 2.11. Can you cherry-pick it to > > >>> ignite-2.11 > > >>> branch? And please fill release notes or delete flag. > > > > On 2021/06/30 07:55:04, Nikita Amelchev > > wrote: > > > Hello, Alexey. > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It > > > fixes > > > incorrect values of cache, cache groups, data region metrics after > > > cluster reactivation. > > > WDYT? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov > > > : > > >> > > >> Ok, we can add this fix to release scope. > > >> > > >> On 2021/06/29 08:36:00, Сурков Александр > > >>> Викторович wrote: > > >>> Hi Alexey. > > >>> > > >>> I think need add ticket: JmxMetricExporter fails to export > > >>> discovery metrics - > > >>> https://issues.apache.org/jira/browse/IGNITE-14376 > > >>> > > >>> On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > > -- > > > Best wishes, > > > Amelchev Nikita > > > > > >>> > > >>> > > >>> > > >>> -- > > >>> Best wishes, > > >>> Amelchev Nikita > > >>> >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
I personally trust opinion of Nikolay and Maxim, we can consider both as blockers. Just an idea to consider: For fixed ticket/PR (https://issues.apache.org/jira/browse/IGNITE-15170) most likely we don't need to re-run performance tests. If second issue has no impact on performance, we can take perf results from rc.-1 and run only functional tests for rc.0. On 2021/07/22 04:44:01, "Николай Ижиков" wrote: > +1 to fix both prior to release > > Отправлено с iPhone > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov написал(а): > > > > Folks, > > > > We've faced [1][2] issues related to the new functionality added to > > the 2.11 release (it will be safe to merge to the release branch). > > From my point of view, both of them are critical and must be included > > in the 2.11 release. > > The [2] is ready for merge. The [1] will be completed by the end of this > > week. > > > > Please share your thoughts. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov wrote: > >> > >> Folks, > >> > >> Since the release branch was created some time ago, should we bump up > >> the master branch version to the next one? > >> > >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov wrote: > >>> > >>> Hi, Pavel. > >>> > >>> I think, it looks like blocker. Please cherry-pick it to 2.11 release > >>> branch > >>> > >>> On 2021/07/01 09:29:57, Pavel Pereslegin wrote: > Hello, Alexey! > > Is it possible to include a hotfix that corrects the command syntax > output in the control script? [1] > > This bug can significantly complicate the use of the snapshot restore > function (one of the important features of 2.11). In addition, this > may raise a number of questions to the product support, which we can > prevent by adding this patch in 2.11. > > This patch does not affect any functions other than the "help" output > of the control script. > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > > > Hi, Iilya! > > > > As I can see, this feature highly improves debugging during incidents. > > So I think we can call it blocker and cherry-pick to ignite-2.11 branch > > > > On 2021/06/30 20:26:43, Shishkov Ilya wrote: > >> Hello, Alexey! > >> Is it possible to add system views for BaselineNode attributes [1] and > >> corresponding documentation [2] to 2.11? > >> > >> 1. https://issues.apache.org/jira/browse/IGNITE-15007 > >> 2. https://issues.apache.org/jira/browse/IGNITE-15028 > >> > >> ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > >> > >>> Thanks! I have cherry-picked the commit to the 2.11 branch. > >>> > >>> ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > Hi, Nikita! > > I think it's important fix and should be included in 2.11 release. > I've > >>> tagged ticket by fixVersion 2.11. Can you cherry-pick it to > >>> ignite-2.11 > >>> branch? And please fill release notes or delete flag. > > On 2021/06/30 07:55:04, Nikita Amelchev wrote: > > Hello, Alexey. > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It fixes > > incorrect values of cache, cache groups, data region metrics after > > cluster reactivation. > > WDYT? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : > >> > >> Ok, we can add this fix to release scope. > >> > >> On 2021/06/29 08:36:00, Сурков Александр > >>> Викторович wrote: > >>> Hi Alexey. > >>> > >>> I think need add ticket: JmxMetricExporter fails to export > >>> discovery metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > >>> > >>> On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > -- > > Best wishes, > > Amelchev Nikita > > > >>> > >>> > >>> > >>> -- > >>> Best wishes, > >>> Amelchev Nikita > >>> > >> > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hi, Maxim. It looks like critical bugs, so we should wait these tickets. On 2021/07/21 23:36:25, Maxim Muzafarov wrote: > Folks, > > We've faced [1][2] issues related to the new functionality added to > the 2.11 release (it will be safe to merge to the release branch). > From my point of view, both of them are critical and must be included > in the 2.11 release. > The [2] is ready for merge. The [1] will be completed by the end of this week. > > Please share your thoughts. > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov wrote: > > > > Folks, > > > > Since the release branch was created some time ago, should we bump up > > the master branch version to the next one? > > > > On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov wrote: > > > > > > Hi, Pavel. > > > > > > I think, it looks like blocker. Please cherry-pick it to 2.11 release > > > branch > > > > > > On 2021/07/01 09:29:57, Pavel Pereslegin wrote: > > > > Hello, Alexey! > > > > > > > > Is it possible to include a hotfix that corrects the command syntax > > > > output in the control script? [1] > > > > > > > > This bug can significantly complicate the use of the snapshot restore > > > > function (one of the important features of 2.11). In addition, this > > > > may raise a number of questions to the product support, which we can > > > > prevent by adding this patch in 2.11. > > > > > > > > This patch does not affect any functions other than the "help" output > > > > of the control script. > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > > > > > > > > > Hi, Iilya! > > > > > > > > > > As I can see, this feature highly improves debugging during > > > > > incidents. So I think we can call it blocker and cherry-pick to > > > > > ignite-2.11 branch > > > > > > > > > > On 2021/06/30 20:26:43, Shishkov Ilya wrote: > > > > > > Hello, Alexey! > > > > > > Is it possible to add system views for BaselineNode attributes [1] > > > > > > and > > > > > > corresponding documentation [2] to 2.11? > > > > > > > > > > > > 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > > > > > 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > > > > > > > > > > > ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > > > > > > > > > > > > > Thanks! I have cherry-picked the commit to the 2.11 branch. > > > > > > > > > > > > > > ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov > > > > > > > : > > > > > > > > > > > > > > > > Hi, Nikita! > > > > > > > > > > > > > > > > I think it's important fix and should be included in 2.11 > > > > > > > > release. I've > > > > > > > tagged ticket by fixVersion 2.11. Can you cherry-pick it to > > > > > > > ignite-2.11 > > > > > > > branch? And please fill release notes or delete flag. > > > > > > > > > > > > > > > > On 2021/06/30 07:55:04, Nikita Amelchev > > > > > > > > wrote: > > > > > > > > > Hello, Alexey. > > > > > > > > > > > > > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It > > > > > > > > > fixes > > > > > > > > > incorrect values of cache, cache groups, data region metrics > > > > > > > > > after > > > > > > > > > cluster reactivation. > > > > > > > > > WDYT? > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > > > > > > > > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov > > > > > > > > > : > > > > > > > > > > > > > > > > > > > > Ok, we can add this fix to release scope. > > > > > > > > > > > > > > > > > > > > On 2021/06/29 08:36:00, Сурков Александр > > > > > > > Викторович wrote: > > > > > > > > > > > Hi Alexey. > > > > > > > > > > > > > > > > > > > > > > I think need add ticket: JmxMetricExporter fails to export > > > > > > > discovery metrics - > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > > > > > > > > > > > > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov > > > > > > > > > > > wrote: > > > > > > > > > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Best wishes, > > > > > > > > > Amelchev Nikita > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Best wishes, > > > > > > > Amelchev Nikita > > > > > > > > > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
+1 to fix both prior to release Отправлено с iPhone > 22 июля 2021 г., в 02:36, Maxim Muzafarov написал(а): > > Folks, > > We've faced [1][2] issues related to the new functionality added to > the 2.11 release (it will be safe to merge to the release branch). > From my point of view, both of them are critical and must be included > in the 2.11 release. > The [2] is ready for merge. The [1] will be completed by the end of this week. > > Please share your thoughts. > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov wrote: >> >> Folks, >> >> Since the release branch was created some time ago, should we bump up >> the master branch version to the next one? >> >>> On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov wrote: >>> >>> Hi, Pavel. >>> >>> I think, it looks like blocker. Please cherry-pick it to 2.11 release branch >>> >>> On 2021/07/01 09:29:57, Pavel Pereslegin wrote: Hello, Alexey! Is it possible to include a hotfix that corrects the command syntax output in the control script? [1] This bug can significantly complicate the use of the snapshot restore function (one of the important features of 2.11). In addition, this may raise a number of questions to the product support, which we can prevent by adding this patch in 2.11. This patch does not affect any functions other than the "help" output of the control script. [1] https://issues.apache.org/jira/browse/IGNITE-14989 чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > Hi, Iilya! > > As I can see, this feature highly improves debugging during incidents. So > I think we can call it blocker and cherry-pick to ignite-2.11 branch > > On 2021/06/30 20:26:43, Shishkov Ilya wrote: >> Hello, Alexey! >> Is it possible to add system views for BaselineNode attributes [1] and >> corresponding documentation [2] to 2.11? >> >> 1. https://issues.apache.org/jira/browse/IGNITE-15007 >> 2. https://issues.apache.org/jira/browse/IGNITE-15028 >> >> ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : >> >>> Thanks! I have cherry-picked the commit to the 2.11 branch. >>> >>> ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : Hi, Nikita! I think it's important fix and should be included in 2.11 release. I've >>> tagged ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11 >>> branch? And please fill release notes or delete flag. On 2021/06/30 07:55:04, Nikita Amelchev wrote: > Hello, Alexey. > > I suggest adding to the 2.11 scope the resolved issue [1]. It fixes > incorrect values of cache, cache groups, data region metrics after > cluster reactivation. > WDYT? > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : >> >> Ok, we can add this fix to release scope. >> >> On 2021/06/29 08:36:00, Сурков Александр >>> Викторович wrote: >>> Hi Alexey. >>> >>> I think need add ticket: JmxMetricExporter fails to export >>> discovery metrics - https://issues.apache.org/jira/browse/IGNITE-14376 >>> >>> On 2021/06/15 14:43:55, Alexey Gidaspov wrote: Apache Ignite 2.11 Code Freeze started now> > > > > -- > Best wishes, > Amelchev Nikita > >>> >>> >>> >>> -- >>> Best wishes, >>> Amelchev Nikita >>> >>
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, We've faced [1][2] issues related to the new functionality added to the 2.11 release (it will be safe to merge to the release branch). >From my point of view, both of them are critical and must be included in the 2.11 release. The [2] is ready for merge. The [1] will be completed by the end of this week. Please share your thoughts. [1] https://issues.apache.org/jira/browse/IGNITE-15146 [2] https://issues.apache.org/jira/browse/IGNITE-15170 On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov wrote: > > Folks, > > Since the release branch was created some time ago, should we bump up > the master branch version to the next one? > > On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov wrote: > > > > Hi, Pavel. > > > > I think, it looks like blocker. Please cherry-pick it to 2.11 release branch > > > > On 2021/07/01 09:29:57, Pavel Pereslegin wrote: > > > Hello, Alexey! > > > > > > Is it possible to include a hotfix that corrects the command syntax > > > output in the control script? [1] > > > > > > This bug can significantly complicate the use of the snapshot restore > > > function (one of the important features of 2.11). In addition, this > > > may raise a number of questions to the product support, which we can > > > prevent by adding this patch in 2.11. > > > > > > This patch does not affect any functions other than the "help" output > > > of the control script. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > > > > > > > Hi, Iilya! > > > > > > > > As I can see, this feature highly improves debugging during incidents. > > > > So I think we can call it blocker and cherry-pick to ignite-2.11 branch > > > > > > > > On 2021/06/30 20:26:43, Shishkov Ilya wrote: > > > > > Hello, Alexey! > > > > > Is it possible to add system views for BaselineNode attributes [1] and > > > > > corresponding documentation [2] to 2.11? > > > > > > > > > > 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > > > > 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > > > > > > > > > ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > > > > > > > > > > > Thanks! I have cherry-picked the commit to the 2.11 branch. > > > > > > > > > > > > ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > > > > > > > > > > > > > Hi, Nikita! > > > > > > > > > > > > > > I think it's important fix and should be included in 2.11 > > > > > > > release. I've > > > > > > tagged ticket by fixVersion 2.11. Can you cherry-pick it to > > > > > > ignite-2.11 > > > > > > branch? And please fill release notes or delete flag. > > > > > > > > > > > > > > On 2021/06/30 07:55:04, Nikita Amelchev > > > > > > > wrote: > > > > > > > > Hello, Alexey. > > > > > > > > > > > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It > > > > > > > > fixes > > > > > > > > incorrect values of cache, cache groups, data region metrics > > > > > > > > after > > > > > > > > cluster reactivation. > > > > > > > > WDYT? > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > > > > > > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov > > > > > > > > : > > > > > > > > > > > > > > > > > > Ok, we can add this fix to release scope. > > > > > > > > > > > > > > > > > > On 2021/06/29 08:36:00, Сурков Александр > > > > > > Викторович wrote: > > > > > > > > > > Hi Alexey. > > > > > > > > > > > > > > > > > > > > I think need add ticket: JmxMetricExporter fails to export > > > > > > discovery metrics - > > > > > > https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > > > > > > > > > > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov > > > > > > > > > > wrote: > > > > > > > > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Best wishes, > > > > > > > > Amelchev Nikita > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best wishes, > > > > > > Amelchev Nikita > > > > > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Folks, Since the release branch was created some time ago, should we bump up the master branch version to the next one? On Thu, 1 Jul 2021 at 17:15, Alexey Gidaspov wrote: > > Hi, Pavel. > > I think, it looks like blocker. Please cherry-pick it to 2.11 release branch > > On 2021/07/01 09:29:57, Pavel Pereslegin wrote: > > Hello, Alexey! > > > > Is it possible to include a hotfix that corrects the command syntax > > output in the control script? [1] > > > > This bug can significantly complicate the use of the snapshot restore > > function (one of the important features of 2.11). In addition, this > > may raise a number of questions to the product support, which we can > > prevent by adding this patch in 2.11. > > > > This patch does not affect any functions other than the "help" output > > of the control script. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > > > > > Hi, Iilya! > > > > > > As I can see, this feature highly improves debugging during incidents. So > > > I think we can call it blocker and cherry-pick to ignite-2.11 branch > > > > > > On 2021/06/30 20:26:43, Shishkov Ilya wrote: > > > > Hello, Alexey! > > > > Is it possible to add system views for BaselineNode attributes [1] and > > > > corresponding documentation [2] to 2.11? > > > > > > > > 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > > > 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > > > > > > > ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > > > > > > > > > Thanks! I have cherry-picked the commit to the 2.11 branch. > > > > > > > > > > ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > > > > > > > > > > > Hi, Nikita! > > > > > > > > > > > > I think it's important fix and should be included in 2.11 release. > > > > > > I've > > > > > tagged ticket by fixVersion 2.11. Can you cherry-pick it to > > > > > ignite-2.11 > > > > > branch? And please fill release notes or delete flag. > > > > > > > > > > > > On 2021/06/30 07:55:04, Nikita Amelchev > > > > > > wrote: > > > > > > > Hello, Alexey. > > > > > > > > > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It > > > > > > > fixes > > > > > > > incorrect values of cache, cache groups, data region metrics after > > > > > > > cluster reactivation. > > > > > > > WDYT? > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > > > > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov > > > > > > > : > > > > > > > > > > > > > > > > Ok, we can add this fix to release scope. > > > > > > > > > > > > > > > > On 2021/06/29 08:36:00, Сурков Александр > > > > > Викторович wrote: > > > > > > > > > Hi Alexey. > > > > > > > > > > > > > > > > > > I think need add ticket: JmxMetricExporter fails to export > > > > > discovery metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > > > > > > > > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov > > > > > > > > > wrote: > > > > > > > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Best wishes, > > > > > > > Amelchev Nikita > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best wishes, > > > > > Amelchev Nikita > > > > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hi, Pavel. I think, it looks like blocker. Please cherry-pick it to 2.11 release branch On 2021/07/01 09:29:57, Pavel Pereslegin wrote: > Hello, Alexey! > > Is it possible to include a hotfix that corrects the command syntax > output in the control script? [1] > > This bug can significantly complicate the use of the snapshot restore > function (one of the important features of 2.11). In addition, this > may raise a number of questions to the product support, which we can > prevent by adding this patch in 2.11. > > This patch does not affect any functions other than the "help" output > of the control script. > > [1] https://issues.apache.org/jira/browse/IGNITE-14989 > > чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > > > Hi, Iilya! > > > > As I can see, this feature highly improves debugging during incidents. So I > > think we can call it blocker and cherry-pick to ignite-2.11 branch > > > > On 2021/06/30 20:26:43, Shishkov Ilya wrote: > > > Hello, Alexey! > > > Is it possible to add system views for BaselineNode attributes [1] and > > > corresponding documentation [2] to 2.11? > > > > > > 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > > 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > > > > > ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > > > > > > > Thanks! I have cherry-picked the commit to the 2.11 branch. > > > > > > > > ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > > > > > > > > > Hi, Nikita! > > > > > > > > > > I think it's important fix and should be included in 2.11 release. > > > > > I've > > > > tagged ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11 > > > > branch? And please fill release notes or delete flag. > > > > > > > > > > On 2021/06/30 07:55:04, Nikita Amelchev wrote: > > > > > > Hello, Alexey. > > > > > > > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It fixes > > > > > > incorrect values of cache, cache groups, data region metrics after > > > > > > cluster reactivation. > > > > > > WDYT? > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : > > > > > > > > > > > > > > Ok, we can add this fix to release scope. > > > > > > > > > > > > > > On 2021/06/29 08:36:00, Сурков Александр > > > > Викторович wrote: > > > > > > > > Hi Alexey. > > > > > > > > > > > > > > > > I think need add ticket: JmxMetricExporter fails to export > > > > discovery metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > > > > > > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > > > > > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best wishes, > > > > > > Amelchev Nikita > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best wishes, > > > > Amelchev Nikita > > > > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hello, Alexey! Is it possible to include a hotfix that corrects the command syntax output in the control script? [1] This bug can significantly complicate the use of the snapshot restore function (one of the important features of 2.11). In addition, this may raise a number of questions to the product support, which we can prevent by adding this patch in 2.11. This patch does not affect any functions other than the "help" output of the control script. [1] https://issues.apache.org/jira/browse/IGNITE-14989 чт, 1 июл. 2021 г. в 11:56, Alexey Gidaspov : > > Hi, Iilya! > > As I can see, this feature highly improves debugging during incidents. So I > think we can call it blocker and cherry-pick to ignite-2.11 branch > > On 2021/06/30 20:26:43, Shishkov Ilya wrote: > > Hello, Alexey! > > Is it possible to add system views for BaselineNode attributes [1] and > > corresponding documentation [2] to 2.11? > > > > 1. https://issues.apache.org/jira/browse/IGNITE-15007 > > 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > > > ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > > > > > Thanks! I have cherry-picked the commit to the 2.11 branch. > > > > > > ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > > > > > > > Hi, Nikita! > > > > > > > > I think it's important fix and should be included in 2.11 release. I've > > > tagged ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11 > > > branch? And please fill release notes or delete flag. > > > > > > > > On 2021/06/30 07:55:04, Nikita Amelchev wrote: > > > > > Hello, Alexey. > > > > > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It fixes > > > > > incorrect values of cache, cache groups, data region metrics after > > > > > cluster reactivation. > > > > > WDYT? > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : > > > > > > > > > > > > Ok, we can add this fix to release scope. > > > > > > > > > > > > On 2021/06/29 08:36:00, Сурков Александр > > > Викторович wrote: > > > > > > > Hi Alexey. > > > > > > > > > > > > > > I think need add ticket: JmxMetricExporter fails to export > > > discovery metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > > > > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > > > > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best wishes, > > > > > Amelchev Nikita > > > > > > > > > > > > > > > > > -- > > > Best wishes, > > > Amelchev Nikita > > > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hi, Iilya! As I can see, this feature highly improves debugging during incidents. So I think we can call it blocker and cherry-pick to ignite-2.11 branch On 2021/06/30 20:26:43, Shishkov Ilya wrote: > Hello, Alexey! > Is it possible to add system views for BaselineNode attributes [1] and > corresponding documentation [2] to 2.11? > > 1. https://issues.apache.org/jira/browse/IGNITE-15007 > 2. https://issues.apache.org/jira/browse/IGNITE-15028 > > ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > > > Thanks! I have cherry-picked the commit to the 2.11 branch. > > > > ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > > > > > Hi, Nikita! > > > > > > I think it's important fix and should be included in 2.11 release. I've > > tagged ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11 > > branch? And please fill release notes or delete flag. > > > > > > On 2021/06/30 07:55:04, Nikita Amelchev wrote: > > > > Hello, Alexey. > > > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It fixes > > > > incorrect values of cache, cache groups, data region metrics after > > > > cluster reactivation. > > > > WDYT? > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : > > > > > > > > > > Ok, we can add this fix to release scope. > > > > > > > > > > On 2021/06/29 08:36:00, Сурков Александр > > Викторович wrote: > > > > > > Hi Alexey. > > > > > > > > > > > > I think need add ticket: JmxMetricExporter fails to export > > discovery metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > > > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best wishes, > > > > Amelchev Nikita > > > > > > > > > > > > -- > > Best wishes, > > Amelchev Nikita > > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hello, Alexey! Is it possible to add system views for BaselineNode attributes [1] and corresponding documentation [2] to 2.11? 1. https://issues.apache.org/jira/browse/IGNITE-15007 2. https://issues.apache.org/jira/browse/IGNITE-15028 ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev : > Thanks! I have cherry-picked the commit to the 2.11 branch. > > ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > > > Hi, Nikita! > > > > I think it's important fix and should be included in 2.11 release. I've > tagged ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11 > branch? And please fill release notes or delete flag. > > > > On 2021/06/30 07:55:04, Nikita Amelchev wrote: > > > Hello, Alexey. > > > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It fixes > > > incorrect values of cache, cache groups, data region metrics after > > > cluster reactivation. > > > WDYT? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : > > > > > > > > Ok, we can add this fix to release scope. > > > > > > > > On 2021/06/29 08:36:00, Сурков Александр > Викторович wrote: > > > > > Hi Alexey. > > > > > > > > > > I think need add ticket: JmxMetricExporter fails to export > discovery metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > > > > > > -- > > > Best wishes, > > > Amelchev Nikita > > > > > > > -- > Best wishes, > Amelchev Nikita >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Thanks! I have cherry-picked the commit to the 2.11 branch. ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov : > > Hi, Nikita! > > I think it's important fix and should be included in 2.11 release. I've > tagged ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11 > branch? And please fill release notes or delete flag. > > On 2021/06/30 07:55:04, Nikita Amelchev wrote: > > Hello, Alexey. > > > > I suggest adding to the 2.11 scope the resolved issue [1]. It fixes > > incorrect values of cache, cache groups, data region metrics after > > cluster reactivation. > > WDYT? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : > > > > > > Ok, we can add this fix to release scope. > > > > > > On 2021/06/29 08:36:00, Сурков Александр > > > Викторович wrote: > > > > Hi Alexey. > > > > > > > > I think need add ticket: JmxMetricExporter fails to export discovery > > > > metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > > > > > > -- > > Best wishes, > > Amelchev Nikita > > -- Best wishes, Amelchev Nikita
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hi, Nikita! I think it's important fix and should be included in 2.11 release. I've tagged ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11 branch? And please fill release notes or delete flag. On 2021/06/30 07:55:04, Nikita Amelchev wrote: > Hello, Alexey. > > I suggest adding to the 2.11 scope the resolved issue [1]. It fixes > incorrect values of cache, cache groups, data region metrics after > cluster reactivation. > WDYT? > > [1] https://issues.apache.org/jira/browse/IGNITE-14990 > > вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : > > > > Ok, we can add this fix to release scope. > > > > On 2021/06/29 08:36:00, Сурков Александр > > Викторович wrote: > > > Hi Alexey. > > > > > > I think need add ticket: JmxMetricExporter fails to export discovery > > > metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > > > > > > On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > > > Apache Ignite 2.11 Code Freeze started now> > > > > > > > > -- > Best wishes, > Amelchev Nikita >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hello, Alexey. I suggest adding to the 2.11 scope the resolved issue [1]. It fixes incorrect values of cache, cache groups, data region metrics after cluster reactivation. WDYT? [1] https://issues.apache.org/jira/browse/IGNITE-14990 вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov : > > Ok, we can add this fix to release scope. > > On 2021/06/29 08:36:00, Сурков Александр > Викторович wrote: > > Hi Alexey. > > > > I think need add ticket: JmxMetricExporter fails to export discovery > > metrics - https://issues.apache.org/jira/browse/IGNITE-14376 > > > > On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > > Apache Ignite 2.11 Code Freeze started now> > > > -- Best wishes, Amelchev Nikita
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Ok, we can add this fix to release scope. On 2021/06/29 08:36:00, Сурков Александр Викторович wrote: > Hi Alexey. > > I think need add ticket: JmxMetricExporter fails to export discovery metrics > - https://issues.apache.org/jira/browse/IGNITE-14376 > > On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > > Apache Ignite 2.11 Code Freeze started now> > >
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hi Alexey. I think need add ticket: JmxMetricExporter fails to export discovery metrics - https://issues.apache.org/jira/browse/IGNITE-14376 On 2021/06/15 14:43:55, Alexey Gidaspov wrote: > Apache Ignite 2.11 Code Freeze started now> > smime.p7s Description: S/MIME cryptographic signature
[Announcement] Apache Ignite 2.11 Code Freeze started
Apache Ignite 2.11 Code Freeze started now
