Re: Ignite compilation fails in IntelliJ IDEA (IgniteLinkTaglet)

Hi Pavel, please go to "Project Structure | Project Settings | Modules", find module "ignite-tools", open tab "Sources" and mark folder "src/main/java11" as "excluded". Should help. This happens from time to time if you switch from a very old branch (like "ignite-2.5") to a fresh branch like "mas

Re: [DISCUSSION] Cache warmup

Hi, Stan! As a result of personal correspondence I realized that you are right about making changes: 1)Move warm-up configuration to org.apache.ignite.configuration.DataRegionConfiguration#setWarmUpConfiguration; 2)Start warming up for each region sequentially; 3)Improving warm-up interface: pa

Re: Ignite compilation fails in IntelliJ IDEA (IgniteLinkTaglet)

Ivan, Thanks for the suggestion. Unfortunately, it does not help - Idea does not let me apply the changes: `Content root "/home/pavel/w/ignite" is defined for modules "apache-ignite" and "ignite". Two modules in a project cannot share the same content root.` Clearly I'm doing something wrong - m

Re: Ignite compilation fails in IntelliJ IDEA (IgniteLinkTaglet)

Hi Pavel, this issue is unrelated to your problem, but yes, it wouldn't allow you to save changes. This sucks. You should remove one of those modules in your settings, they point on the same pom.xml, this means that this is the same module twice in your settings. пн, 10 авг. 2020 г. в 11:24, Pave

Re: Ignite compilation fails in IntelliJ IDEA (IgniteLinkTaglet)

Hi Pavel, You can do the same action in Project tree -> right button on java11 -> Mark directory as -> excluded --  Best regards, Anton Kalashnikov 10.08.2020, 11:34, "Ivan Bessonov" : > Hi Pavel, > > this issue is unrelated to your problem, but yes, it wouldn't allow you to > save changes. >

Re: Ignite compilation fails in IntelliJ IDEA (IgniteLinkTaglet)

Anton, this worked, thank you! On Mon, Aug 10, 2020 at 1:06 PM Anton Kalashnikov wrote: > Hi Pavel, > > You can do the same action in Project tree -> right button on java11 -> > Mark directory as -> excluded > > -- > Best regards, > Anton Kalashnikov > > > > 10.08.2020, 11:34, "Ivan Bessonov" :

Re: [DISCUSSION] Cache warmup

Hi, Stan again :-) I suggest adding a little more flexibility to configuration: 1)Add default warm-up configuration for all regions into org.apache.ignite.configuration.DataStorageConfiguration#setDefaultWarmUpConfiguration 2)Add a NoOp strategy for turning off heating of a specific region Thus,

Re: [DISCUSSION] Cache warmup

All of this looks awesome, covers the use cases I know about. Thanks! Stan > On 10 Aug 2020, at 15:39, ткаленко кирилл wrote: > > Hi, Stan again :-) > > I suggest adding a little more flexibility to configuration: > 1)Add default warm-up configuration for all regions into > org.apache.ignite.

[jira] [Created] (IGNITE-13345) Warming up node

Kirill Tkalenko created IGNITE-13345: Summary: Warming up node Key: IGNITE-13345 URL: https://issues.apache.org/jira/browse/IGNITE-13345 Project: Ignite Issue Type: New Feature

Re: [DISCUSSION] Cache warmup

Great! Then I proceed to ticket https://issues.apache.org/jira/browse/IGNITE-13345. 10.08.2020, 16:30, "Stanislav Lukyanov" : > All of this looks awesome, covers the use cases I know about. > Thanks! > > Stan > >>  On 10 Aug 2020, at 15:39, ткаленко кирилл wrote: >> >>  Hi, Stan again :-) >> >>

Too many messages in log in case of exceptions in user computations.

In case of errors in user computations the Ignite Compute Grid produces a lot of errors into the log. In the worst way it produces the next messages: 1. Failed to execute job: … 2. Failed to reduce job results: … 3. Failed to execute task: … There is a suggestion to decrease log level

Re: Too many messages in log in case of exceptions in user computations.

Hello, Vasiliy. This messages are shown on the different nodes, isn’t it? > 10 авг. 2020 г., в 18:34, Vasiliy Sisko написал(а): > > In case of errors in user computations the Ignite Compute Grid produces a > lot of errors into the log. > In the worst way it produces the next messages: >1. F

Re: [DISCUSSION] Add index rebuild time metrics

Folks, Sorry for coming late to the party. I've taken a look at this issue during review. How can a local number of processed keys can help us to understand when index rebuild will be finished? We can't compare metric value with cache.size(). First one is node-local, while cache size covers all p

Re: [BLOG] Apache Ignite Extensions

Hi Saikat, The weekly routines of an Apache Ignite committer :) I believe that Ignite application developers would love to learn insights from this article and eventually get modular-based Ignite integrations. So, with(out) your permission sharing the article via @user list. Excellent article and

Re: IGNITE-12363 Migrate Camel module to ignite-extensions

Saikat, Thanks for moving Camel to the extensions repo. Please feel free to merge the change. Looks good to me. - Denis On Sat, Aug 8, 2020 at 10:38 AM Saikat Maitra wrote: > Hi, > > I have created the following PRs for migration of camel module. > > Jira https://issues.apache.org/jira/browse

Re: [DISCUSSION] Add index rebuild time metrics

Hi, Ivan! For this you can use org.apache.ignite.cache.CacheMetrics#IsIndexRebuildInProgress > How can a local number of processed keys can help us to understand when > index rebuild will be finished? This metric can be used only for local node, to get size of cache use org.apache.ignite.intern

Re: [DISCUSSION] Add index rebuild time metrics

> > This metric can be used only for local node, to get size of cache use > org.apache.ignite.internal.processors.cache.CacheMetricsImpl#getCacheSize. Got it, agree. If there is a lot of data in node that can be rebuilt, percentage may > change very rarely and may not give an estimate of how muc

Apache Ignite Board report, August, 2020

Dear Apache Ignite community, PMC should submit the board report, not later than 12 August. Previous board with drafted publicly with sharing with all developers community. Let us try it one more time. Please share your thoughts on what might be added to the board meeting agenda. ## Description:

Re: Apache Ignite Board report, August, 2020

Hi Dmitry, Thanks for sending the draft. I would suggest mentioning the following in the project activity section: - Ignite Extensions project that decouples the core features from 3rd-party integrations is being moved forward rapidly

[MTCGA]: new failures in builds [5530437] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master TcpDiscoveryPendingMessageDeliveryTest.testPendingMessagesOverflow https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=528088

Re: Apache Ignite Board report, August, 2020

Hi Denis, thank you for your valuable feedback, this makes perfect sense to include all these points. A little bit off-top: PMCs, would anybody like to be a PMC representative for the new group in addition to Denis M.? It is recommended to have 2 members at least to make sure that an event using

Re: Apache Ignite Board report, August, 2020

> > A little bit off-top: PMCs, would anybody like to be a PMC representative > for the new group in addition to Denis M.? It is recommended to have 2 > members at least to make sure that an event using the Apache-project brand > follows branding policy and all other Apache guidelines? This shoul

Re: [BLOG] Apache Ignite Extensions

Hi Denis, Thank you so much and glad you shared the article with the user community. We are close to finishing up the migration of modules as planned and will start preparing for releases. Regards, Saikat On Mon, Aug 10, 2020 at 12:12 PM Denis Magda wrote: > Hi Saikat, > > The weekly routine

Re: IGNITE-12363 Migrate Camel module to ignite-extensions

Hi Denis, Thank you for reviewing the changes. I will go ahead and merge the changes. Regards, Saikat On Mon, Aug 10, 2020 at 12:14 PM Denis Magda wrote: > Saikat, > > Thanks for moving Camel to the extensions repo. Please feel free to merge > the change. Looks good to me. > > - > Denis > > >

Re: Apache Ignite Board report, August, 2020

Hi Dmitriy, Denis I am thinking if it would be good to add that this year a dedicated track for Apache Ignite is available in APACHECON 2020 @Home on September 29th. https://apachecon.com/acah2020/tracks/ Regards, Saikat On Mon, Aug 10, 2020 at 7:18 PM Denis Magda wrote: > > > > A little bit

Re: Apache Ignite 3.0

Hi Val, Thank you for sharing the page and your efforts in compiling the features list, I am thinking since it is a major version release then shall we include a section for deprecated features and add changes as mentioned in our Apache Ignite 3.0 Wishlist https://cwiki.apache.org/confluence/disp

[MTCGA]: new failures in builds [5530982] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master TcpDiscoveryPendingMessageDeliveryTest.testDeliveryAllFailedMessagesInCorrectOrder https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&

[jira] [Created] (IGNITE-13346) “Joining persistence node to in-memory cluster couldn't be allowed” Verification is too strict

YuJue Li created IGNITE-13346: - Summary: “Joining persistence node to in-memory cluster couldn't be allowed” Verification is too strict Key: IGNITE-13346 URL: https://issues.apache.org/jira/browse/IGNITE-13346

Re: [DISCUSSION] Add index rebuild time metrics

Hi, Ivan! What precision would be sufficient? > If the progress is very slow, I don't see issues with tracking it if the > percentage float has enough precision. I think we can add a mention getting cache size. > 1. Gain an understanding that local cache size > (CacheMetricsImpl#getCacheSize) sho