Re: [ANNOUNCE] Release pyignite-0.5.1
Since there is no any activity and contradiction, I decided to announce code freeze now. Release candidates for voting will be available tomorrow вт, 20 июл. 2021 г. в 09:45, Ivan Daschinsky : > Igniters! > > I suppose it is time to release pyignite 0.5.1. There are few good > features available and some users are eager to try it. > > 1. Added ability to record clients' events by event listeners. This is a > quite agile mechanism, and it allows writing custom metrics, tracing and > debugging. > 2. Added debug logging > > When implementing these features, I have found and fixed a few bugs thanks > for excessive logging and events. (see release notes of [1]). > Also I want to implement one minor feature that can be useful (ability to > set handshake timeout). > I am going to implement it in a few days. [2] > > Full list of tickets for release is here [3] > > I think that code freeze will be at 15:00 UTC 07/23. And on monday, 07/26 > we will publish a release candidate for voting. > > WDYT? > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-15102 > [2] -- https://issues.apache.org/jira/browse/IGNITE-15118 > [3] -- > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20python-0.5.1 > -- Sincerely yours, Ivan Daschinskiy
Re: [ANNOUNCE] Release pyignite-0.5.1
Branch for release -- https://github.com/apache/ignite-python-thin-client/tree/pyignite-0.5.1 Release notes -- https://github.com/apache/ignite-python-thin-client/blob/pyignite-0.5.1/RELEASE_NOTES.txt чт, 22 июл. 2021 г. в 12:18, Ivan Daschinsky : > Since there is no any activity and contradiction, I decided to announce > code freeze now. Release candidates for voting will be available tomorrow > > вт, 20 июл. 2021 г. в 09:45, Ivan Daschinsky : > >> Igniters! >> >> I suppose it is time to release pyignite 0.5.1. There are few good >> features available and some users are eager to try it. >> >> 1. Added ability to record clients' events by event listeners. This is a >> quite agile mechanism, and it allows writing custom metrics, tracing and >> debugging. >> 2. Added debug logging >> >> When implementing these features, I have found and fixed a few bugs >> thanks for excessive logging and events. (see release notes of [1]). >> Also I want to implement one minor feature that can be useful (ability to >> set handshake timeout). >> I am going to implement it in a few days. [2] >> >> Full list of tickets for release is here [3] >> >> I think that code freeze will be at 15:00 UTC 07/23. And on monday, 07/26 >> we will publish a release candidate for voting. >> >> WDYT? >> >> >> [1] -- https://issues.apache.org/jira/browse/IGNITE-15102 >> [2] -- https://issues.apache.org/jira/browse/IGNITE-15118 >> [3] -- >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%20python-0.5.1 >> > > > -- > Sincerely yours, Ivan Daschinskiy > -- Sincerely yours, Ivan Daschinskiy
Re: Your Nabble Forum
Probably, this is a reason why our Nabble's dev list forum got out of sync. The latest message is dated as June 20th. Yeah, it's sad that ASF's mailing lists are not visible to search engines like Google. That's a big deal for those who search for a topic on search engines (99% of the human beings?). Let's think, I see three options here: - Search for an alternate mail archiving solution that can be indexed by Google - Talk to the ASF mates, probably there is a solution for user lists - Give up the reins to StackOverflow that will naturally become a primary communication channel for the user-related questions. -- Denis - Denis On Thu, Jul 22, 2021 at 12:33 AM Ilya Kasnacheev wrote: > Hello! > > They say they don't host mailing list archives anymore. I wonder what they > expect us to do here. > > I think it's a pity since Nabble had a great deal of SEO visibility, > especially for user list. Unfortunately, Pony Mail is almost useless in > that regard. > > Regards, > -- > Ilya Kasnacheev > > > ср, 21 июл. 2021 г. в 23:23, : > > > We are downsizing Nabble to one server. If you want to preserve your > > forum: > > > > http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > Then you should follow the instructions here: > > > > http://support.nabble.com/Downsizing-Nabble-tp7609715.html > > >
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: Your Nabble Forum
Folks, My vote goes for ponymail. Actually it is a project under ASF itself, it is the part of Incubator. If we have a contributor who is aware about CEO setup, we can suggest help and solve that issue for all ASF projects at once. https://github.com/apache/incubator-ponymail https://ponymail.incubator.apache.org/support.html https://lists.apache.org/list.html?us...@ponymail.apache.org I personaly use only lists.apache.org. And since at my dayjob gmail is blocked, I also reply here. What do you think? Sincerely, Dmitriy Pavlov On 2021/07/22 10:58:28, Denis Magda wrote: > Probably, this is a reason why our Nabble's dev list forum got out of sync. > The latest message is dated as June 20th. > > Yeah, it's sad that ASF's mailing lists are not visible to search engines > like Google. That's a big deal for those who search for a topic on search > engines (99% of the human beings?). Let's think, I see three options here: > >- Search for an alternate mail archiving solution that can be indexed by >Google >- Talk to the ASF mates, probably there is a solution for user lists >- Give up the reins to StackOverflow that will naturally become a >primary communication channel for the user-related questions. > > -- > Denis > > - > Denis > > On Thu, Jul 22, 2021 at 12:33 AM Ilya Kasnacheev > wrote: > > > Hello! > > > > They say they don't host mailing list archives anymore. I wonder what they > > expect us to do here. > > > > I think it's a pity since Nabble had a great deal of SEO visibility, > > especially for user list. Unfortunately, Pony Mail is almost useless in > > that regard. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 21 июл. 2021 г. в 23:23, : > > > > > We are downsizing Nabble to one server. If you want to preserve your > > > forum: > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > > Then you should follow the instructions here: > > > > > > http://support.nabble.com/Downsizing-Nabble-tp7609715.html > > > > > >
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: Your Nabble Forum
+1 for pony mail. It is a great tool with nice interface with zero ads stuff. чт, 22 июл. 2021 г. в 15:26, Dmitry Pavlov : > Folks, > > My vote goes for ponymail. Actually it is a project under ASF itself, it > is the part of Incubator. > > If we have a contributor who is aware about CEO setup, we can suggest help > and solve that issue for all ASF projects at once. > > https://github.com/apache/incubator-ponymail > https://ponymail.incubator.apache.org/support.html > https://lists.apache.org/list.html?us...@ponymail.apache.org > > I personaly use only lists.apache.org. And since at my dayjob gmail is > blocked, I also reply here. > > What do you think? > > Sincerely, > Dmitriy Pavlov > > On 2021/07/22 10:58:28, Denis Magda wrote: > > Probably, this is a reason why our Nabble's dev list forum got out of > sync. > > The latest message is dated as June 20th. > > > > Yeah, it's sad that ASF's mailing lists are not visible to search engines > > like Google. That's a big deal for those who search for a topic on search > > engines (99% of the human beings?). Let's think, I see three options > here: > > > >- Search for an alternate mail archiving solution that can be indexed > by > >Google > >- Talk to the ASF mates, probably there is a solution for user lists > >- Give up the reins to StackOverflow that will naturally become a > >primary communication channel for the user-related questions. > > > > -- > > Denis > > > > - > > Denis > > > > On Thu, Jul 22, 2021 at 12:33 AM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> > > wrote: > > > > > Hello! > > > > > > They say they don't host mailing list archives anymore. I wonder what > they > > > expect us to do here. > > > > > > I think it's a pity since Nabble had a great deal of SEO visibility, > > > especially for user list. Unfortunately, Pony Mail is almost useless in > > > that regard. > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > ср, 21 июл. 2021 г. в 23:23, : > > > > > > > We are downsizing Nabble to one server. If you want to preserve your > > > > forum: > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > > > > Then you should follow the instructions here: > > > > > > > > http://support.nabble.com/Downsizing-Nabble-tp7609715.html > > > > > > > > > > -- Sincerely yours, Ivan Daschinskiy
Re: Your Nabble Forum
Dmitry, Ivan, It would be ideal if we can open up PonyMail archives for search engines. It might be just one setting on a web server configuration. Dmitry, any idea whom we should start discussing this with at ASF? -- Denis - Denis On Thu, Jul 22, 2021 at 3:32 PM Ivan Daschinsky wrote: > +1 for pony mail. It is a great tool with nice interface with zero ads > stuff. > > чт, 22 июл. 2021 г. в 15:26, Dmitry Pavlov : > > > Folks, > > > > My vote goes for ponymail. Actually it is a project under ASF itself, it > > is the part of Incubator. > > > > If we have a contributor who is aware about CEO setup, we can suggest > help > > and solve that issue for all ASF projects at once. > > > > https://github.com/apache/incubator-ponymail > > https://ponymail.incubator.apache.org/support.html > > https://lists.apache.org/list.html?us...@ponymail.apache.org > > > > I personaly use only lists.apache.org. And since at my dayjob gmail is > > blocked, I also reply here. > > > > What do you think? > > > > Sincerely, > > Dmitriy Pavlov > > > > On 2021/07/22 10:58:28, Denis Magda wrote: > > > Probably, this is a reason why our Nabble's dev list forum got out of > > sync. > > > The latest message is dated as June 20th. > > > > > > Yeah, it's sad that ASF's mailing lists are not visible to search > engines > > > like Google. That's a big deal for those who search for a topic on > search > > > engines (99% of the human beings?). Let's think, I see three options > > here: > > > > > >- Search for an alternate mail archiving solution that can be > indexed > > by > > >Google > > >- Talk to the ASF mates, probably there is a solution for user lists > > >- Give up the reins to StackOverflow that will naturally become a > > >primary communication channel for the user-related questions. > > > > > > -- > > > Denis > > > > > > - > > > Denis > > > > > > On Thu, Jul 22, 2021 at 12:33 AM Ilya Kasnacheev < > > ilya.kasnach...@gmail.com> > > > wrote: > > > > > > > Hello! > > > > > > > > They say they don't host mailing list archives anymore. I wonder what > > they > > > > expect us to do here. > > > > > > > > I think it's a pity since Nabble had a great deal of SEO visibility, > > > > especially for user list. Unfortunately, Pony Mail is almost useless > in > > > > that regard. > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > > > > > > > > ср, 21 июл. 2021 г. в 23:23, : > > > > > > > > > We are downsizing Nabble to one server. If you want to preserve > your > > > > > forum: > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > > > > > > Then you should follow the instructions here: > > > > > > > > > > http://support.nabble.com/Downsizing-Nabble-tp7609715.html > > > > > > > > > > > > > > > > > -- > Sincerely yours, Ivan Daschinskiy >
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: Your Nabble Forum
Infra group is the ideal forum for this On Thu, 22 Jul 2021, 18:14 Denis Magda, wrote: > Dmitry, Ivan, > > It would be ideal if we can open up PonyMail archives for search engines. > It might be just one setting on a web server configuration. Dmitry, any > idea whom we should start discussing this with at ASF? > > -- > Denis > > - > Denis > > On Thu, Jul 22, 2021 at 3:32 PM Ivan Daschinsky > wrote: > > > +1 for pony mail. It is a great tool with nice interface with zero ads > > stuff. > > > > чт, 22 июл. 2021 г. в 15:26, Dmitry Pavlov : > > > > > Folks, > > > > > > My vote goes for ponymail. Actually it is a project under ASF itself, > it > > > is the part of Incubator. > > > > > > If we have a contributor who is aware about CEO setup, we can suggest > > help > > > and solve that issue for all ASF projects at once. > > > > > > https://github.com/apache/incubator-ponymail > > > https://ponymail.incubator.apache.org/support.html > > > https://lists.apache.org/list.html?us...@ponymail.apache.org > > > > > > I personaly use only lists.apache.org. And since at my dayjob gmail is > > > blocked, I also reply here. > > > > > > What do you think? > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > On 2021/07/22 10:58:28, Denis Magda wrote: > > > > Probably, this is a reason why our Nabble's dev list forum got out of > > > sync. > > > > The latest message is dated as June 20th. > > > > > > > > Yeah, it's sad that ASF's mailing lists are not visible to search > > engines > > > > like Google. That's a big deal for those who search for a topic on > > search > > > > engines (99% of the human beings?). Let's think, I see three options > > > here: > > > > > > > >- Search for an alternate mail archiving solution that can be > > indexed > > > by > > > >Google > > > >- Talk to the ASF mates, probably there is a solution for user > lists > > > >- Give up the reins to StackOverflow that will naturally become a > > > >primary communication channel for the user-related questions. > > > > > > > > -- > > > > Denis > > > > > > > > - > > > > Denis > > > > > > > > On Thu, Jul 22, 2021 at 12:33 AM Ilya Kasnacheev < > > > ilya.kasnach...@gmail.com> > > > > wrote: > > > > > > > > > Hello! > > > > > > > > > > They say they don't host mailing list archives anymore. I wonder > what > > > they > > > > > expect us to do here. > > > > > > > > > > I think it's a pity since Nabble had a great deal of SEO > visibility, > > > > > especially for user list. Unfortunately, Pony Mail is almost > useless > > in > > > > > that regard. > > > > > > > > > > Regards, > > > > > -- > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > ср, 21 июл. 2021 г. в 23:23, : > > > > > > > > > > > We are downsizing Nabble to one server. If you want to preserve > > your > > > > > > forum: > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > > > > > > > > Then you should follow the instructions here: > > > > > > > > > > > > http://support.nabble.com/Downsizing-Nabble-tp7609715.html > > > > > > > > > > > > > > > > > > > > > > > > -- > > Sincerely yours, Ivan Daschinskiy > > >
Re: [Discussion] Race on heartbeat update in checkpoint thread
Hi guys, I think updateHeartBeat() method was misused in the future listener and this must be fixed. Actually, GridWorker.heartbeatTs Javadoc says that field is updated by the worker itself. It is consistent with WorkProgressDispatcher.updateHearbeat() javadoc, which said "Notifying dispatcher that work is in progress and thread didn't freeze." GridWorker.heartbeatTs field is marked volatile just to provide consistent visibility guarantee to a watcher. So, CheckpointPagesWriter violates this contract, when runs in another thread(s). But it works fine just because the main (Checkpointer) thread waits for all the Writers to finish their work before it can fall into the blocking section, therefore there is no race possible. As for the broken case, there are 2 possible solutions, 1. Main thread must wait for all children's tasks to finish before going into the blocking section. 2. Or make updateHeartbeat consistent with the blockingSectionBegin/End. Seems, there is no need to mark the method as synchronized, but use call AtomicLongFieldUpdater.getAndUpdate(this, v -> v == Long.MAX_VALUE ? v : U.currentTimeMillis()). I'd suggest * Remove the "thread" mentioning from WorkProgressDispatcher interface to avoid confusion with the current usage and make WorkProgressDispatcher more general. * Avoid unsafe heartbeatUpdater leak to the outside via wrapping CheckpointContextImpl.heartbeatUpdater instance to perform consistent heartbeat update from p.2 above. Does it make sense? On Wed, Jul 21, 2021 at 11:12 AM Alex Plehanov wrote: > Ilya, > > Race only affects the future listener (which only updates heartbeat), but > not checkpoint listeners, so no other bugs possible caused by this race > except wrong heartbeat update. > > As I've written before, I think it's not a good idea to wait for other > threads by the critical thread in the blocking section. If these threads > are not monitored we can never detect lack of progress and never trigger > the failure handler. Perhaps a good solution will be to register async > threads as critical threads (additionally to waiting for these threads in > the blocing section) and update their own heartbeat. But the current fix is > required too, to avoid such problems for other critical threads in the > future. > > ср, 21 июл. 2021 г. в 06:29, Ilya Kazakov : > > > 1. > > I mean calling listeners in CheckpointWorkflow.markCheckpointBegin(): > > > > This > > -- > > for (CheckpointListener lsnr : dbLsnrs) > > lsnr.beforeCheckpointBegin(ctx0); > > > > ctx0.awaitPendingTasksFinished(); > > -- > > > > And this: > > > > -- > > // Listeners must be invoked before we write checkpoint record to WAL. > > for (CheckpointListener lsnr : dbLsnrs) > > lsnr.onMarkCheckpointBegin(ctx0); > > > > ctx0.awaitPendingTasksFinished(); > > -- > > > > Inside lsnr.beforeCheckpointBegin(ctx0) and > > lsnr.onMarkCheckpointBegin(ctx0) we call CheckpointContextImpl.executor() > > which submit heartbeat update tasks in threadpool. But due to a bug in > > registration, ctx0.awaitPendingTasksFinished() do not work correctly. > > Checpoint thread does not wait for all tasks to complete and moves on. > > > > This could lead to other bugs because as written in the comment "// > > Listeners must be invoked before we write checkpoint record to WAL." > > > > 2. > > About the fix. > > Yes, the fix resolves the issue, but does not resolve the root cause - a > > race between checkpoint thread and threads run in asyncRunner. Also, as I > > understand, there should be no attempts to update heartbeat inside > > blockingSection, but the fix does not exclude such attempts but blocks > them. > > > > 3. > > But my main point is that it looks strange to update the heartbeat of > > thread A from thread B. It's like doing artificial respiration and chest > > compressions. Thread A is waiting on async tasks completion, but these > > tasks are updating progress of thread A. I suppose that blockingSection > was > > designed for such situations when the thread is waiting for something and > > does not perform any progress. > > > > вт, 20 июл. 2021 г. в 21:43, Ivan Daschinsky : > > > >> +1 For current fix. Code is clean and understandable. I suppose that the > >> current fix is a correct variant to update heartbeatTs. > >> > >> вт, 20 июл. 2021 г. в 16:13, Alex Plehanov : > >> > >> > Hello, Ilya > >> > > >> > > But anyway, I propose to remove the update of the heartbeat from > other > >> > threads altogether and wrap the call to listeners in a > blockingSection. > >> > I don't quite understand your proposal. Which call to listeners do you > >> > mean? If we wrap the listener into the blocking section the result > will > >> be > >> > the same. > >> > Alternatively, I think we can wrap awaitPendingTasksFinished into the > >> > blocking section, this will also solve the pr
Apache Ignite Repo 403 Forbidden
This looks very similar to an issue from last year: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-downloads-are-redirecting-from-https-to-http-td31428.html When I attempt to run `apt-get update` on Ubuntu 18.04 with the Apache Ignite repository in /etc/apt/sources.list, the update fails due to an https to http redirect. Here's the output from stdout: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Hit:1 http://azure.archive.ubuntu.com/ubuntu bionic InRelease Get:2 http://azure.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:4 http://azure.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:6 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease Err:3 https://dl.bintray.com/apache/ignite-deb apache-ignite InRelease 403 Forbidden [IP: 52.38.32.109 443] Reading package lists... E: Failed to fetch http://apache.org/dist/ignite/deb/dists/apache-ignite/InRelease 403 Forbidden [IP: 52.38.32.109 443] E: The repository 'http://apache.org/dist/ignite/deb apache-ignite InRelease' is not signed.
Re: Apache Ignite Repo 403 Forbidden
Hello! + Petr Bintray went away, and I guess we have to re-publish these to jfrog. Regards, -- Ilya Kasnacheev чт, 22 июл. 2021 г. в 20:39, Mustafa Sunka : > This looks very similar to an issue from last year: > > http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-downloads-are-redirecting-from-https-to-http-td31428.html > > When I attempt to run `apt-get update` on Ubuntu 18.04 with the Apache > Ignite repository in /etc/apt/sources.list, the update fails due to an > https to http redirect. Here's the output from stdout: > > > WARNING: apt does not have a stable CLI interface. Use with caution in > scripts. > > Hit:1 http://azure.archive.ubuntu.com/ubuntu bionic InRelease > Get:2 http://azure.archive.ubuntu.com/ubuntu bionic-updates InRelease > [88.7 kB] > Get:4 http://azure.archive.ubuntu.com/ubuntu bionic-backports InRelease > [74.6 kB] > Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease > Hit:6 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease > Err:3 https://dl.bintray.com/apache/ignite-deb apache-ignite InRelease > 403 Forbidden [IP: 52.38.32.109 443] > Reading package lists... > E: Failed to fetch > http://apache.org/dist/ignite/deb/dists/apache-ignite/InRelease 403 > Forbidden [IP: 52.38.32.109 443] > E: The repository 'http://apache.org/dist/ignite/deb apache-ignite > InRelease' is not signed. >
Re: Apache Ignite 3 Alpha 2 webinar follow up questions
Hi Courtney, Thanks for your feedback. I've gone through the questions and have no the whole picture of your use case. Would you please clarify how you exactly use the Ignite? what are the integration points? and maybe share some experience with using Ignite SPIs? We'll keep the information in mind while developing the Ignite, because this may help us to make a better product. By the way, I'll try to answer the questions. > 1. Schema change - does that include the ability to change the types of > fields/columns? Yes, we plan to support transparent conversion to a wider type on-fly (e.g. 'int' to 'long'). This is a major point of our Live-schema concept. In fact, there is no need to convert data on all the nodes in a synchronous way as old SQL databases do (if one supports though), we are going to support multiple schema versions and convert data on-demand on a per-row basis to the latest version, then write-back the row. More complex things like 'String' -> 'int' are out of scope for now because it requires the execution of a user code on the critical path. The limitation here is column MUST NOT be indexed, because an index over the data of different kinds is impossible. > 2. Will the new guaranteed consistency between APIs also mean SQL will > gain transaction support? Yes, we plan to have Transactional SQL. DDL will be non-transactional though, and I wonder if the one supports this. Ignite 3 will operate with Rows underneath, but classic Table API and Key-value will be available to a user at the same time and with all consistency guarantees. > 3. Has there been any decision about how much of Calcite will be exposed > to the client? When using thick clients, it'll be hugely beneficial to be > able to work with Calcite APIs directly to provide custom rules and > optimizations to better suit organization needs As of now, we have no plans to expose any Calcite API to a user. AFAIK, we have our custom Calcite convention, custom rules that are aware of distributed environment, and additional AST nodes. The rules MUST correctly propagate internal information about data distribution, so I'm not sure want to give low-level access to them. > We Index into Solr and use the Solr indices Ignite 1-2 has poor support for TEXT queries, which is totally unconfigurable. Also, Lucene indices underneath are NOT persistent that requires too much effort to fix it. GeoSpatial index has the same issues, we decided to drop them along with Indexing SPI at all. However, you can find the activity on dev-list on the Index Query topic. Guys are going to add IndexQuery (a scan query over the sorted index which can use simple conditions) in Ignite 2. We also plan to have the same functionality, maybe it is possible to add full-text search support here. Will it work for you, what do you think? >4. Will the unified storage model enable different versions of Ignite to > be in the cluster when persistence is enabled so that rolling restarts can > be done? I'm not sure a rolling upgrade (RU) will be available because too much compatibility issues should be resolved to make RU possible under the load without downtime. Maybe it makes sense to provide some grid mode (maintenance mode) for RU purposes that will block all the user load but allow upgrade the grid. E.g. for the pure in-memory case. Persistence compatibility should be preserved as it works for Ignite 2. >5. Will it be possible to provide a custom cache store still and will > these changes enable custom cache stores to be queryable from SQL? I'm not sure I fully understand this. 1. Usually, SQL is about indices. Ignite can't perform a query over the unindexed data. 2. Fullscan over the cache that contains only part of data + scan the CacheStore, then merging the results is a pain. Most likely, running a query over CacheStore directly will be a simpler way, and even more performant. Shared CacheStore (same for all nodes) will definitely kill the performance in that case. So, the preliminary loadCache() call looks like a good compromise. 3. Splitting query into 2 parts to run on Ignite and to run on CacheStore looks possible with Calcite, but I think it impractical because in general, neither CacheStore nor database structure are aware of the data partitioning. 4. Transactions can't be supported in case of direct CacheStore access, because even if the underlying database supports 2-phase commit, which is a rare case, the recovery protocol looks hard. Just looks like this feature doesn't worth it. > 6. This question wasn't mine but I was going to ask it as well: What > will happen to the Indexing API since H2 is being removed? As I wrote above, Indexing SPI will be dropped, but IndexQuery will be added. > 1. As I mentioned above, we Index into Solr, in earlier versions of > our product we used the indexing SPI to index into Lucene on the Ignite > nodes but this presented so many challenges we ultimately abandoned it an
Re: Apache Ignite Repo 403 Forbidden
Is there a mirror available? I have an app I am trying to rebuild and am unable to proceed without this install. On Thu, Jul 22, 2021 at 5:09 PM Ilya Kasnacheev wrote: > Hello! > > + Petr > > Bintray went away, and I guess we have to re-publish these to jfrog. > > Regards, > -- > Ilya Kasnacheev > > > чт, 22 июл. 2021 г. в 20:39, Mustafa Sunka : > > > This looks very similar to an issue from last year: > > > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_Apache-2DIgnite-2Ddownloads-2Dare-2Dredirecting-2Dfrom-2Dhttps-2Dto-2Dhttp-2Dtd31428.html&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=Oy3AYmpDoeav2VjaPGM-zWUKLgzX42RUO1GsDRsdy44&e= > > > > When I attempt to run `apt-get update` on Ubuntu 18.04 with the Apache > > Ignite repository in /etc/apt/sources.list, the update fails due to an > > https to http redirect. Here's the output from stdout: > > > > > > WARNING: apt does not have a stable CLI interface. Use with caution in > > scripts. > > > > Hit:1 > https://urldefense.proofpoint.com/v2/url?u=http-3A__azure.archive.ubuntu.com_ubuntu&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=2Ov6DP1Bap0srqqc3X-UtLngbcH27ecZ8-mULSqkiTI&e= > bionic InRelease > > Get:2 > https://urldefense.proofpoint.com/v2/url?u=http-3A__azure.archive.ubuntu.com_ubuntu&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=2Ov6DP1Bap0srqqc3X-UtLngbcH27ecZ8-mULSqkiTI&e= > bionic-updates InRelease > > [88.7 kB] > > Get:4 > https://urldefense.proofpoint.com/v2/url?u=http-3A__azure.archive.ubuntu.com_ubuntu&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=2Ov6DP1Bap0srqqc3X-UtLngbcH27ecZ8-mULSqkiTI&e= > bionic-backports InRelease > > [74.6 kB] > > Hit:5 > https://urldefense.proofpoint.com/v2/url?u=http-3A__security.ubuntu.com_ubuntu&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=G6_zzVnIHvOkW-Y3DmaEkgIomjN4ruRMTMjrrzK1IFU&e= > bionic-security InRelease > > Hit:6 > https://urldefense.proofpoint.com/v2/url?u=https-3A__packages.microsoft.com_ubuntu_18.04_prod&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=k2leSDqZA4M0XmZUsXQjt1dz4ItJlOnVUu-jXnZdTes&e= > bionic InRelease > > Err:3 > https://urldefense.proofpoint.com/v2/url?u=https-3A__dl.bintray.com_apache_ignite-2Ddeb&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=O5A9lfplCQ6qcDpU9l0YKopmdV_i8idBbBIfPUe5Upc&e= > apache-ignite InRelease > > 403 Forbidden [IP: > https://urldefense.proofpoint.com/v2/url?u=http-3A__52.38.32.109&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=E2zCjuf9KyZoT04dLgLMzQswdhmmJFy7nUm7y1vGcdw&e= > 443] > > Reading package lists... > > E: Failed to fetch > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__apache.org_dist_ignite_deb_dists_apache-2Dignite_InRelease&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=hy6PkAM2M11njAAzj9aSoUYWRWTnFkLbMpcfRV_vli0&e= > 403 > > Forbidden [IP: > https://urldefense.proofpoint.com/v2/url?u=http-3A__52.38.32.109&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=E2zCjuf9KyZoT04dLgLMzQswdhmmJFy7nUm7y1vGcdw&e= > 443] > > E: The repository ' > https://urldefense.proofpoint.com/v2/url?u=http-3A__apache.org_dist_ignite_deb&d=DwIFaQ&c=f7K5vTjsy0ldRUVHx_C48Q&r=F_pxrwS6ECbSFnH54hVvzyOo5Yb0IvCiswhvjRVXOCs&m=XQgK5pAVCrRiCWaNfbv0pubokT-e6V1EU_ZQrEH8b70&s=rFH6lD19kpqf96es9ta26jHs0pXlzqervXXfqEjW16E&e= > apache-ignite > > InRelease' is not signed. > > > -- *Mustafa Sunka* *DevOps Engineer* *Heartland* +1 585.625.5491 O mustafa.su...@e-hps.com *A Global Payments Company* *NOTICE: This email message is for the sole use of the addressee(s) named above and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this message or any attachments is expressly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies and backups of the original message.* -- NOTICE: This email message is for the sole use of the addressee(s) named above and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this message or any attachments is expressly prohibited. If you are not the intended recipient, please contact the sender by reply email and de
