Re: Adding a system view of recently completed compute tasks

[Zhenya Stanilovsky]

Hi, seems ignite already contain such view [1], plz explain the difference?
thanks.
 
[1]  https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#tasks
 
> 
>> 
>>>Hello everyone!
>>>
>>>I want to add a new system view to get the last N (configurable by system 
>>>property, default 100) completed compute tasks, are there any objections? 
>> 
>> 
>> 
>> 

Adding a system view of recently completed compute tasks

[ткаленко кирилл]

Hello everyone!

I want to add a new system view to get the last N (configurable by system 
property, default 100) completed compute tasks, are there any objections?

[DISCUSSION] IgniteOutOfMemoryException may not be a critical failure

[Alexey Kukushkin]

Hi Igniters,

Currently Ignite treats the "not enough data region capacity" case as a
critical failure and does not allow configuring any of the default critical
failure handlers to ignore that error.

In our company we have different teams using Apache Ignite and none of them
wants to apply a default "stop server" or "restart server" handler when
encountering the problem. We rather want to report this problem to DevOps
and the end users.

We developed a custom failure handler to deal with the problem but the
solution is really clumsy. And the most important thing is we think
treating this problem as a critical failure is not what most users would
want.

What do you think about enhancing Ignite not to treat the "not enough data
region capacity" case as a critical failure?

We opened IGNITE-16272  for
this discussion with the description below:

The Problem
Ignite raises the IgniteOutOfMemoryException
if
a data region size is exceeded when trying to add more data to a cache.
Ignite considers the IgniteOutOfMemoryException as a critical failure. This
causes shutting down the Ignite server with the default failure handler.

However, reaching the data region capacity does not seem to be such a
critical problem requiring the server shutdown or restart. For example, in
our application we just want to report this problem back to the users and
notify the DevOps without applying the critical failure handler. To achieve
that, we had to define a custom FailureHandler that detects and ignores the
IgniteOutOfMemoryException and all the caused by the
IgniteOutOfMemoryException, allowing the final exception to reach the
application. This solution is clumsy and unreliable since it uses the
internal IgniteOutOfMemoryException definition and relies on a complex
secondary exception structure trying to find the IgniteOutOfMemoryException
among the suppressed exception and causes.

Ignite out-of-the-box failure handlers have the ignoredFailure property
that allows filtering out some kinds of failures. However, the
IgniteOutOfMemoryException is not among the FailureType
that
can be ignored.

The Proposal

   1. Does anyone really want to treat the "data region capacity exceeded"
   problem as a critical failure and stop or restart the server?
  - Consider never treating this condition as a critical failure. This
  change is not backward compatible.
  - Or add another item to the FailureType enumeration to optionally
  allow the users not to have that treated as a critical failure. This is
  backward-compatible.
   2. Make the IgniteOutOfMemoryException a public API (now it is in the
   internal package)
   3. Consider renaming IgniteOutOfMemoryException (for example, to
   something like NotEnoughStorageException) since the current name is similar
   to a really critical and usually unrecoverable Java's OutOfMemoryError
   although the IgniteOutOfMemoryException is not that critical.

--
Best regards,
Alexey

Re: NON-CODE contributions

[Kseniya Romanova]

Hi,  Manuel! Great to hear from you.
I've added your Ignite tutorial and blog post to the system:
https://recognition.gridgain.com/profile/aaecf4f3-b7f5-451c-bb38-0467836a910e

Please ping as you publish anything new about Ignite.

BTW, what do you think about sharing the experience of using Ignite with
Mule or Spring on one of the Virtual meetups?


вт, 11 янв. 2022 г. в 17:20, Manuel Núñez Sánchez :

> Hi, Team!
>
> I am CTO at Hawkore and I have been developing projects using Apache
> Ignite for many years, since version 1.5!
>
> I would be very grateful if you would include any of my contributions to
> the project.
>
> Thanks a lot!
>
> Best!
>
> LinkedIn profile: www.linkedin.com/in/mnusan
>
> Code contributions to Spring Data Extension for Apache Ignite (2.0 and
> 2.2), since Apache Ignite 2.9.0:
>
>
> https://github.com/apache/ignite-extensions/tree/master/modules/spring-data-2.0-ext
>
>
> https://github.com/apache/ignite-extensions/tree/master/modules/spring-data-2.2-ext
>
>
> Some blog entries and GitHub examples:
>
> About affinity data collocation:
>
> https://blog.hawkore.com/2020/05/22/affinity-data-collocation/
>
>
> About bringing the power of Apache Ignite and GridGain to Mule
> (Orchestration of services and systems integration):
>
> https://blog.hawkore.com/2020/04/27/apache-ignite-connector-mule-starting/
>
>
> https://blog.hawkore.com/2020/05/27/gridgain-connector-mule-starting/
>
>
> About distributed computation using Apache Ignite and GridGain with Mule
> on Kubernetes (SQL, locks, queues and cache operations):
>
> https://github.com/hawkore/examples-spring-boot-mule4-kubernetes
>
> https://github.com/hawkore/examples-spring-boot-mule4-kubernetes-gridgain
>
>
>
>
>  *Manuel Núñez *
>   CTO
>
>   manuel.nu...@hawkore.com
>
>   Paseo de la Castellana 182
>   28046 Madrid
>
>   Cell +34 626 698 331
>   Tel   +34 910 059 985
>
>   www.hawkore.com
>
>

NON-CODE contributions

[Manuel Núñez Sánchez]

Hi, Team!

I am CTO at Hawkore and I have been developing projects using Apache Ignite for 
many years, since version 1.5!

I would be very grateful if you would include any of my contributions to the 
project.

Thanks a lot!

Best!

LinkedIn profile: www.linkedin.com/in/mnusan

Code contributions to Spring Data Extension for Apache Ignite (2.0 and 2.2), 
since Apache Ignite 2.9.0:


https://github.com/apache/ignite-extensions/tree/master/modules/spring-data-2.0-ext


https://github.com/apache/ignite-extensions/tree/master/modules/spring-data-2.2-ext


Some blog entries and GitHub examples:

About affinity data collocation:  

https://blog.hawkore.com/2020/05/22/affinity-data-collocation/


About bringing the power of Apache Ignite and GridGain to Mule (Orchestration 
of services and systems integration): 


https://blog.hawkore.com/2020/04/27/apache-ignite-connector-mule-starting/  

https://blog.hawkore.com/2020/05/27/gridgain-connector-mule-starting/


About distributed computation using Apache Ignite and GridGain with Mule on 
Kubernetes (SQL, locks, queues and cache operations):

https://github.com/hawkore/examples-spring-boot-mule4-kubernetes


https://github.com/hawkore/examples-spring-boot-mule4-kubernetes-gridgain

  

 Manuel Núñez 
  CTO
 
  manuel.nu...@hawkore.com 
  
  Paseo de la Castellana 182
  28046 Madrid

  Cell +34 626 698 331
  Tel   +34 910 059 985

  www.hawkore.com

Re: Request for contributors permissions

[Pavel Tupitsyn]

Hi Brennan,

I've granted you contributor access in JIRA.
Welcome to the Apache Ignite community!

The ticket looks good to me, I've only set the fix version.
Will review the PR now.

Thanks,
Pavel

On Tue, Jan 11, 2022 at 5:15 PM Brennan Fox  wrote:

> Hi Ignite team,
>
> May I please have contributor access to the Ignite Jira project?
>
> I have opened an issue in Jira (
> https://issues.apache.org/jira/browse/IGNITE-16252 ), and I already have a
> PR open to fix it ( https://github.com/apache/ignite/pull/9718 )
>
> Also, are there any details (fixVersion etc) I should add or edit in the
> Jira bug?
>
> Many thanks in advance!
>

Request for contributors permissions

[Brennan Fox]

Hi Ignite team,

May I please have contributor access to the Ignite Jira project?

I have opened an issue in Jira (
https://issues.apache.org/jira/browse/IGNITE-16252 ), and I already have a
PR open to fix it ( https://github.com/apache/ignite/pull/9718 )

Also, are there any details (fixVersion etc) I should add or edit in the
Jira bug?

Many thanks in advance!

Re: About IEP-37

[Chang Chen]

For example, please take a look at
https://issues.apache.org/jira/browse/CALCITE-4013. I just tested it with
tpch q7 which is much slower than non-top-down style optimizter.

top-down : about 1 minute
non top-down:  < 20 seconds

Thanks
- Chang


Alex Plehanov  于2022年1月11日周二 17:25写道：

> Hello,
>
> Why do you think CALCITE-4052 is a blocker for top-down optimization
> in Ignite? As far as I understand, CALCITE-4052 is an umbrella ticket to
> implement trait propagation for all physical relational operators of the
> "enumerable convention" in Calcite. Ignite doesn't use enumerable
> convention and has its own convention with its own physical relational
> operators. Can you please explain your concerns?
>
> сб, 8 янв. 2022 г. в 16:14, Chang Chen :
>
> > Hi, ignite guys
> >
> > I thought that Apache Ignite does what apache drill does[1], but it makes
> > me surprised that Ignite uses a top-down calcite optimizer [2]. But I
> > believe some issues blocks top-down [3].
> >
> > Except for apace drill, both hazelcast[4] and Flink[5] split optimization
> > into two independent phases - logical and physical.
> >
> > Why did Ignite make such a technical decision?
> >
> > Thanks
> > - Chang
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine
> > [2] https://issues.apache.org/jira/browse/IGNITE-13117
> > [3] https://issues.apache.org/jira/browse/CALCITE-4052
> > [4] https://github.com/hazelcast/hazelcast
> > [5] https://github.com/apache/flink
> >
>

Re: [VOTE] Release Apache Ignite 2.12.0 RC2

[Ivan Daschinsky]

+1 From me.

Checked Ignite.C++ on ubuntu 20.04 and windows:
1. Building and installing all components (Core, thin client and ODBC)
2. Run examples.

Checked building 64-bit and 32-bit ODBC driver installers (python + pyodbc)
Checked ODBC driver installers, shipped with ignite. (python + pyodbc)

вт, 11 янв. 2022 г. в 12:49, Anton Vinogradov :

> +1
>
> On Tue, Jan 11, 2022 at 11:35 AM Maxim Muzafarov 
> wrote:
>
> > +1
> >
> > On Tue, 11 Jan 2022 at 11:31, Nikolay Izhikov 
> wrote:
> > >
> > > +1
> > >
> > > > 11 янв. 2022 г., в 02:38, Vladimir Steshin 
> > написал(а):
> > > >
> > > > +1
> > > >
> > > > 10.01.2022 15:52, Nikita Amelchev пишет:
> > > >> Dear Community,
> > > >>
> > > >> The release candidate (2.12.0-rc2) is ready.
> > > >>
> > > >> I have uploaded a release candidate to:
> > > >> https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc2/
> > > >> https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc2/
> > > >>
> > > >> The following staging can be used for testing:
> > > >>
> > https://repository.apache.org/content/repositories/orgapacheignite-1539
> > > >>
> > > >> Tag name is 2.12.0-rc2:
> > > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.12.0-rc2
> > > >>
> > > >> RELEASE_NOTES:
> > > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.12
> > > >>
> > > >> Complete list of resolved issues:
> > > >>
> >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> > > >>
> > > >> DEVNOTES:
> > > >>
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.12
> > > >>
> > > >> Additional checks have been performed (available for users included
> > > >> into the release group on TeamCity).
> > > >>
> > > >> TC [Check RC: Licenses, compile, chksum]
> > > >>
> >
> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6266150?showRootCauses=false=true
> > > >>
> > > >> TC [2] Compare w/ Previous Release
> > > >>
> >
> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6266148?showRootCauses=false=true
> > > >>
> > > >> The vote is formal, see voting guidelines
> > > >> https://www.apache.org/foundation/voting.html
> > > >>
> > > >> +1 - to accept Apache Ignite 2.12.0-rc2
> > > >> 0 - don't care either way
> > > >> -1 - DO NOT accept Apache Ignite Ignite 2.12.0-rc2 (explain why)
> > > >>
> > > >> See notes on how to verify release here
> > > >> https://www.apache.org/info/verification.html
> > > >> and
> > > >>
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> > > >>
> > > >> This vote will be open until Thu Jan 13, 2022, 16:00 UTC. Please,
> > > >> write me down the thread if you need additional time to check the
> > > >> release.
> > > >>
> >
> https://www.timeanddate.com/countdown/vote?iso=20220113T16=0=VOTE+on+the+Apache+Ignite+Release+2.12.0+RC2=sanserif
> > > >>
> > >
> >
>


-- 
Sincerely yours, Ivan Daschinskiy

Re: A new feedback has been added : 50

[Pavel Tupitsyn]

For some reason, .NET docs were not built during 2.11.1 release.
They are missing both on the website and in zip files.
Unfortunately, TeamCity logs are no longer available, so the reason is not
clear.

I've double-checked that the upcoming 2.12 release does not have this
problem [1]

[1] https://lists.apache.org/thread/9ls3n1cg3bmqz1l683jzdwokfmnygrgw


On Tue, Jan 11, 2022 at 11:55 AM Ilya Kasnacheev 
wrote:

> Indeed https://ignite.apache.org/releases/latest/dotnetdoc/ won't open.
> --
> Ilya Kasnacheev
>
>
> пн, 10 янв. 2022 г. в 05:22, Bugyard :
>
>> A new feedback has been added, go to bugyard.io to see all the details...
>>
>> https://bugyard.io
>>
>> A new feedback has been added
>>
>> "You .NET API Document has been generating a 404 for some time now from
>> the menu. Browsing the directory, it seems to be missing. It thought it
>> would ultimately be fixed, but it seems not. It use to be available. I
>> would but appreciate having access. Thanks you in advance."   by
>> louis.fournier
>>
>> View feedback
>> https://app.bugyard.io/web/app/rycqZJDyY/f/61db9235b6a71d0014891b7e
>
>

Re: [VOTE] Release Apache Ignite 2.12.0 RC2

[Anton Vinogradov]

+1

On Tue, Jan 11, 2022 at 11:35 AM Maxim Muzafarov  wrote:

> +1
>
> On Tue, 11 Jan 2022 at 11:31, Nikolay Izhikov  wrote:
> >
> > +1
> >
> > > 11 янв. 2022 г., в 02:38, Vladimir Steshin 
> написал(а):
> > >
> > > +1
> > >
> > > 10.01.2022 15:52, Nikita Amelchev пишет:
> > >> Dear Community,
> > >>
> > >> The release candidate (2.12.0-rc2) is ready.
> > >>
> > >> I have uploaded a release candidate to:
> > >> https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc2/
> > >> https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc2/
> > >>
> > >> The following staging can be used for testing:
> > >>
> https://repository.apache.org/content/repositories/orgapacheignite-1539
> > >>
> > >> Tag name is 2.12.0-rc2:
> > >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.12.0-rc2
> > >>
> > >> RELEASE_NOTES:
> > >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.12
> > >>
> > >> Complete list of resolved issues:
> > >>
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> > >>
> > >> DEVNOTES:
> > >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.12
> > >>
> > >> Additional checks have been performed (available for users included
> > >> into the release group on TeamCity).
> > >>
> > >> TC [Check RC: Licenses, compile, chksum]
> > >>
> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6266150?showRootCauses=false=true
> > >>
> > >> TC [2] Compare w/ Previous Release
> > >>
> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6266148?showRootCauses=false=true
> > >>
> > >> The vote is formal, see voting guidelines
> > >> https://www.apache.org/foundation/voting.html
> > >>
> > >> +1 - to accept Apache Ignite 2.12.0-rc2
> > >> 0 - don't care either way
> > >> -1 - DO NOT accept Apache Ignite Ignite 2.12.0-rc2 (explain why)
> > >>
> > >> See notes on how to verify release here
> > >> https://www.apache.org/info/verification.html
> > >> and
> > >>
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> > >>
> > >> This vote will be open until Thu Jan 13, 2022, 16:00 UTC. Please,
> > >> write me down the thread if you need additional time to check the
> > >> release.
> > >>
> https://www.timeanddate.com/countdown/vote?iso=20220113T16=0=VOTE+on+the+Apache+Ignite+Release+2.12.0+RC2=sanserif
> > >>
> >
>

Re: About IEP-37

[Alex Plehanov]

Hello,

Why do you think CALCITE-4052 is a blocker for top-down optimization
in Ignite? As far as I understand, CALCITE-4052 is an umbrella ticket to
implement trait propagation for all physical relational operators of the
"enumerable convention" in Calcite. Ignite doesn't use enumerable
convention and has its own convention with its own physical relational
operators. Can you please explain your concerns?

сб, 8 янв. 2022 г. в 16:14, Chang Chen :

> Hi, ignite guys
>
> I thought that Apache Ignite does what apache drill does[1], but it makes
> me surprised that Ignite uses a top-down calcite optimizer [2]. But I
> believe some issues blocks top-down [3].
>
> Except for apace drill, both hazelcast[4] and Flink[5] split optimization
> into two independent phases - logical and physical.
>
> Why did Ignite make such a technical decision?
>
> Thanks
> - Chang
>
> [1]
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine
> [2] https://issues.apache.org/jira/browse/IGNITE-13117
> [3] https://issues.apache.org/jira/browse/CALCITE-4052
> [4] https://github.com/hazelcast/hazelcast
> [5] https://github.com/apache/flink
>

Re: A new feedback has been added : 50

[Ilya Kasnacheev]

Indeed https://ignite.apache.org/releases/latest/dotnetdoc/ won't open.
-- 
Ilya Kasnacheev


пн, 10 янв. 2022 г. в 05:22, Bugyard :

> A new feedback has been added, go to bugyard.io to see all the details...
>
> https://bugyard.io
>
> A new feedback has been added
>
> "You .NET API Document has been generating a 404 for some time now from
> the menu. Browsing the directory, it seems to be missing. It thought it
> would ultimately be fixed, but it seems not. It use to be available. I
> would but appreciate having access. Thanks you in advance."   by
> louis.fournier
>
> View feedback
> https://app.bugyard.io/web/app/rycqZJDyY/f/61db9235b6a71d0014891b7e

Re: [VOTE] Release Apache Ignite 2.12.0 RC2

[Maxim Muzafarov]

+1

On Tue, 11 Jan 2022 at 11:31, Nikolay Izhikov  wrote:
>
> +1
>
> > 11 янв. 2022 г., в 02:38, Vladimir Steshin  написал(а):
> >
> > +1
> >
> > 10.01.2022 15:52, Nikita Amelchev пишет:
> >> Dear Community,
> >>
> >> The release candidate (2.12.0-rc2) is ready.
> >>
> >> I have uploaded a release candidate to:
> >> https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc2/
> >> https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc2/
> >>
> >> The following staging can be used for testing:
> >> https://repository.apache.org/content/repositories/orgapacheignite-1539
> >>
> >> Tag name is 2.12.0-rc2:
> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.12.0-rc2
> >>
> >> RELEASE_NOTES:
> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.12
> >>
> >> Complete list of resolved issues:
> >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> >>
> >> DEVNOTES:
> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.12
> >>
> >> Additional checks have been performed (available for users included
> >> into the release group on TeamCity).
> >>
> >> TC [Check RC: Licenses, compile, chksum]
> >> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6266150?showRootCauses=false=true
> >>
> >> TC [2] Compare w/ Previous Release
> >> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6266148?showRootCauses=false=true
> >>
> >> The vote is formal, see voting guidelines
> >> https://www.apache.org/foundation/voting.html
> >>
> >> +1 - to accept Apache Ignite 2.12.0-rc2
> >> 0 - don't care either way
> >> -1 - DO NOT accept Apache Ignite Ignite 2.12.0-rc2 (explain why)
> >>
> >> See notes on how to verify release here
> >> https://www.apache.org/info/verification.html
> >> and
> >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >>
> >> This vote will be open until Thu Jan 13, 2022, 16:00 UTC. Please,
> >> write me down the thread if you need additional time to check the
> >> release.
> >> https://www.timeanddate.com/countdown/vote?iso=20220113T16=0=VOTE+on+the+Apache+Ignite+Release+2.12.0+RC2=sanserif
> >>
>

Re: [VOTE] Release Apache Ignite 2.12.0 RC2

[Nikolay Izhikov]

+1

> 11 янв. 2022 г., в 02:38, Vladimir Steshin  написал(а):
> 
> +1
> 
> 10.01.2022 15:52, Nikita Amelchev пишет:
>> Dear Community,
>> 
>> The release candidate (2.12.0-rc2) is ready.
>> 
>> I have uploaded a release candidate to:
>> https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc2/
>> https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc2/
>> 
>> The following staging can be used for testing:
>> https://repository.apache.org/content/repositories/orgapacheignite-1539
>> 
>> Tag name is 2.12.0-rc2:
>> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.12.0-rc2
>> 
>> RELEASE_NOTES:
>> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.12
>> 
>> Complete list of resolved issues:
>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
>> 
>> DEVNOTES:
>> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.12
>> 
>> Additional checks have been performed (available for users included
>> into the release group on TeamCity).
>> 
>> TC [Check RC: Licenses, compile, chksum]
>> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6266150?showRootCauses=false=true
>> 
>> TC [2] Compare w/ Previous Release
>> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6266148?showRootCauses=false=true
>> 
>> The vote is formal, see voting guidelines
>> https://www.apache.org/foundation/voting.html
>> 
>> +1 - to accept Apache Ignite 2.12.0-rc2
>> 0 - don't care either way
>> -1 - DO NOT accept Apache Ignite Ignite 2.12.0-rc2 (explain why)
>> 
>> See notes on how to verify release here
>> https://www.apache.org/info/verification.html
>> and
>> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
>> 
>> This vote will be open until Thu Jan 13, 2022, 16:00 UTC. Please,
>> write me down the thread if you need additional time to check the
>> release.
>> https://www.timeanddate.com/countdown/vote?iso=20220113T16=0=VOTE+on+the+Apache+Ignite+Release+2.12.0+RC2=sanserif
>>