Re: IEP-14: Ignite failures handling (Discussion)

As far as shutdown, what we need to implement is “hard shutdown” mode. This is when we first close all network sockets, then cancel all registered futures. This would enough to unblock the cluster and local user threads. ср, 14 марта 2018 г. в 8:40, Vladimir Ozerov : >

Re: IEP-14: Ignite failures handling (Discussion)

Valya, This is very easy to answer - if CommandLineStartup is used, then it is standalone node. In all other cases it is embedded. If node shutdown hangs - just let it continue hanging, so that application admins are able to decide on their own what to do next. Someone would want to get the

Re: Ignite contibutors page

Denis, Please add my name as well. Best Turik Campbell -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: IEP-14: Ignite failures handling (Discussion)

Dmitriy. I think you and other participants of discussion are talking about different cases. May be it be usefull to look at specific cases and discuss each of them separately? I look at IEP page and see following: ``` File IO errors. Usually IOException's threw by read/write operations on

Re: [jira] [Created] (IGNITE-7940) Visor CMD: Support cache.lostPartitions() and ignite.resetLostPartitions().

Issue created. https://ggsystems.atlassian.net/browse/WC-454 On Wed, Mar 14, 2018 at 9:52 AM, Denis Magda wrote: > Alex, > > What's about Web Console? Have you created a similar ticket? > > On Tue, Mar 13, 2018 at 5:29 PM, Alexey Kuznetsov (JIRA) > wrote:

[jira] [Created] (IGNITE-7941) Update dependencies to latest versions and migrate to caret(^) in package.json + package.json.lock

Alexander Kalinin created IGNITE-7941: - Summary: Update dependencies to latest versions and migrate to caret(^) in package.json + package.json.lock Key: IGNITE-7941 URL:

Re: IEP-14: Ignite failures handling (Discussion)

I can tell you as a user that if any library I was using in my application called System.exit without my consent would result in a lot of frustration. If ignite enters an unrecoverable state then I think that is something that should be observable locally, similar to node segmentation and then

Re: [jira] [Created] (IGNITE-7940) Visor CMD: Support cache.lostPartitions() and ignite.resetLostPartitions().

Alex, What's about Web Console? Have you created a similar ticket? On Tue, Mar 13, 2018 at 5:29 PM, Alexey Kuznetsov (JIRA) wrote: > Alexey Kuznetsov created IGNITE-7940: > > > Summary: Visor CMD: Support

Re: Partition recovery issue on partition loss.

This indeed looks like a bigger issue. Basically, there is no clear way (or no way at all) to synchronize code that listens to partition loss event, and the code that calls resetLostPartitions() method. Example scenario: 1. Cache is configured with 3rd party persistence. 2. One or more nodes fail

Re: Partition loss policy - how to use?

Gaurav, I think it make sense to add this for tools. Created issue: https://issues.apache.org/jira/browse/IGNITE-7940 On Wed, Mar 14, 2018 at 1:44 AM, Gaurav Bajaj wrote: > Hi Denis, > Thanks. Document certainly looks useful. Do we have ticket for improvement > in

[jira] [Created] (IGNITE-7940) Visor CMD: Support cache.lostPartitions() and ignite.resetLostPartitions().

Alexey Kuznetsov created IGNITE-7940: Summary: Visor CMD: Support cache.lostPartitions() and ignite.resetLostPartitions(). Key: IGNITE-7940 URL: https://issues.apache.org/jira/browse/IGNITE-7940

Re: IEP-14: Ignite failures handling (Discussion)

Ivan, If grid hangs, graceful shutdown would most likely hang as well. Almost never you can recover from a bad state using graceful procedures. I agree that we should not create two defaults, especially in this case. It's not even strictly defined what is embedded node in Ignite. For example, if

Re: IEP-14: Ignite failures handling (Discussion)

One more note: "kill if standalone, stop if embedded" differs from what you are suggesting "try graceful, then kill process regardless" only in case when graceful shutdown hangs. Do we have understanding, how often does graceful shutdown hang? Obviously, *grid hang* is often case, but it

Re: IEP-14: Ignite failures handling (Discussion)

On Tue, Mar 13, 2018 at 7:13 PM, Ivan Rakov wrote: > I just would like to add my +1 for "kill if standalone, stop if embedded" > default option. My arguments: > > 1) Regarding "If Ignite hangs - it will likely be impossible to stop": > Unfortunately, it's true that Ignite

Re: IEP-14: Ignite failures handling (Discussion)

I just would like to add my +1 for "kill if standalone, stop if embedded" default option. My arguments: 1) Regarding "If Ignite hangs - it will likely be impossible to stop": Unfortunately, it's true that Ignite can hang during stop procedure. However, most of failures described under IEP-14

Re: IGNITE_HOME for persistence

On Tue, Mar 13, 2018 at 7:01 PM, Dmitry Pavlov wrote: > Hi, > > do we have a task to print this warning message? > > It seems we don't print warning currently. > I do not think we have a ticket. As AG mentioned, this is an issue for cases when persistence is disabled as

Re: IEP-14: Ignite failures handling (Discussion)

On Tue, Mar 13, 2018 at 6:55 PM, Dmitry Pavlov wrote: > What do you think if stop is default for all cases? > > Kill is configurable. > > We can consider enforse sockets close for 'stop'. This will allow to ignore > hang node by rest of the cluster. > Dmitriy, I see that

Re: IGNITE_HOME for persistence

Hi, do we have a task to print this warning message? It seems we don't print warning currently. Sincerely, Dmitry Pavlov ср, 31 янв. 2018 г., 0:55 Dmitriy Setrakyan : > I think at this point all we can do is print a warning. However, starting > with 3.0, we should

Re: IEP-14: Ignite failures handling (Discussion)

What do you think if stop is default for all cases? Kill is configurable. We can consider enforse sockets close for 'stop'. This will allow to ignore hang node by rest of the cluster. ср, 14 мар. 2018 г., 1:48 Dmitriy Setrakyan : > Guys, I do not think there is an

Re: IEP-14: Ignite failures handling (Discussion)

Guys, I do not think there is an understanding here. If Ignite hangs - it will likely be impossible to stop. So if you are suggesting "stop if embedded", you might as well suggest "do nothing if embedded". I have seen many Ignite deployments, embedded or not, large and small, and in all those

Re: IGNITE-6879

Hello Roman, It's not a big deal, I've added you to the contributors' list in JIRA. Go ahead and assign the ticket to yourself. Folks, anyway, who can review Roman's contribution that brings Spring 2.0 support to Ignite? -- Denis On Tue, Mar 13, 2018 at 2:21 PM, Роман Меерсон

[jira] [Created] (IGNITE-7939) .NET client node throws IgniteClientDisconnectedCheckedException when listening to EVT_CLIENT_NODE_DISCONNECTED and all Java server nodes exit

Kevin Jin created IGNITE-7939: - Summary: .NET client node throws IgniteClientDisconnectedCheckedException when listening to EVT_CLIENT_NODE_DISCONNECTED and all Java server nodes exit Key: IGNITE-7939 URL:

IGNITE-6879

Hello! I want to work on https://issues.apache.org/jira/browse/IGNITE-6879 issue. Following the rules here https://ignite.apache.org/community/contribute.html#contribute my Jira username is "homich" so assign me to this ticket please. P.S. I found this rules page after I made PR, so sorry for

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Then tell me what to correct and I'll merge the changes. Alternatively, you can send me an SVN patch with changes if it's simples: https://cwiki.apache.org/confluence/display/IGNITE/Website+Development -- Denis On Tue, Mar 13, 2018 at 12:25 PM, Petr Ivanov wrote: > I have

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

I have no access to site and readme.io has no errors. > On 13 Mar 2018, at 22:23, Denis Magda wrote: > > Petr, > > Have you corrected the site and readme.io docs (if it was required)? > > -- > Denis > > On Mon, Mar 12, 2018 at 11:14 PM, Petr Ivanov

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

Petr, Have you corrected the site and readme.io docs (if it was required)? -- Denis On Mon, Mar 12, 2018 at 11:14 PM, Petr Ivanov wrote: > There is an error in RPM documentation on site — missing header for > ignite.repo file and formatting is also wrong. > Otherwise —

Re: Partition loss policy - how to use?

Hi Gaurav, I'm not sure about that, but it sounds like a right addition anyway. Alex K., could you chime in please and clarify if the tools somehow support the loss policies? -- Denis On Tue, Mar 13, 2018 at 11:44 AM, Gaurav Bajaj wrote: > Hi Denis, > Thanks.

Re: Partition loss policy - how to use?

Hi Denis, Thanks. Document certainly looks useful. Do we have ticket for improvement in Webconsole/Visor for marking resetLostPartitions()? Regards, Gaurav On 13-Mar-2018 7:42 PM, "Denis Magda" wrote: For those interested, here is a doc we put together for the partition

Re: Partition loss policy - how to use?

For those interested, here is a doc we put together for the partition policies which considers extra improvements released in 2.4: https://apacheignite.readme.io/v2.4/docs/partition-loss-policies -- Denis On Tue, Mar 6, 2018 at 11:19 AM, Denis Magda wrote: > Hi, > > Here is

Re: Data eviction/expiration from Ignite persistence

Alexey, My understanding was that the expiration policies worked for data in RAM only. Ok, if an expired entry is removed from both RAM and Ignite persistence then what happens if a cache store is used instead of Ignite storage? Do we remove expired entries from RDBMs, Cassandra, etc? My guess

Re: MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

Hi Alexey, Could you help with this question? I've observed such messages, it were probably sent by timeout, but not sure their purpose. Sincerely, Dmitriy Pavlov вт, 13 мар. 2018 г. в 20:58, Maxim Muzafarov : > Hi all, > > I'm working on [1] IgniteClientReconnectCacheTest

Re: Deploying 2.4 artifacts to maven repo

That's not a maven central but rather a 3rd party portal that enlists maven dependencies. We had a conversation about this with INFRA before: https://issues.apache.org/jira/browse/INFRA-13073 I see that Ignite is already in maven central:

Re: IEP-14: Ignite failures handling (Discussion)

+1 for "kill if standalone, stop if embedded" behavior. If the practice shows that the node should be killed regardless of the mode, then it will be an easy change. Now we are just guessing, and common sense suggests going for "kill if standalone, stop if embedded" until we get feedback. - Denis

Re: Apache Ignite community in social network VK.com

Could you add a reference to the group to the "events" section on the site? The section itself needs to be renamed to "Events & Groups" after that. -- Denis 2018-03-13 6:47 GMT-07:00 Dmitry Pavlov : > Hi! We created https://vk.com/apacheignite for Russian speaking

MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

Hi all, I'm working on [1] IgniteClientReconnectCacheTest class with frakly test-case testReconnectCacheDestroyedAndCreated with success rate 32.4%. I've leaved comment in JIRA [2] and new test-case with reproducing this issue. Basicly, when we receiving GridDhtPartitionsSingleMessage with

Re: Apache Ignite nightly release builds

Yes please! :) Sent from my iPhone > On 14/03/2018, at 4:10 AM, Dmitry Pavlov wrote: > > We can start with this approach. And if we will need some staging maven > repo, we can support it later. > > вт, 13 мар. 2018 г. в 18:08, Dmitriy Setrakyan :

Re: Apache Ignite community in social network VK.com

Dmitry, Awesome thing! 2018-03-13 16:47 GMT+03:00 Dmitry Pavlov : > Hi! We created https://vk.com/apacheignite for Russian speaking community. > That will be the hub for Apache Ignite events and resources in Russian. > Follow the group to get latest news and suggest

[GitHub] ignite pull request #3611: Ignite 7751

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3611 ---

[GitHub] ignite pull request #3629: IGNITE-7875: MultiSVM - added Model, Trainer and ...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3629 IGNITE-7875: MultiSVM - added Model, Trainer and Tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7887

[GitHub] ignite pull request #3229: IGNITE-7182: Checkpoint pages: optimize and paral...

Github user dspavlov closed the pull request at: https://github.com/apache/ignite/pull/3229 ---

[jira] [Created] (IGNITE-7938) [ML] Adopt KMeans to the new Partitioned Dataset

Aleksey Zinoviev created IGNITE-7938: Summary: [ML] Adopt KMeans to the new Partitioned Dataset Key: IGNITE-7938 URL: https://issues.apache.org/jira/browse/IGNITE-7938 Project: Ignite

[GitHub] ignite pull request #3628: IGNITE-6879 and migration to spring-data 2.0.5.RE...

GitHub user homich1991 opened a pull request: https://github.com/apache/ignite/pull/3628 IGNITE-6879 and migration to spring-data 2.0.5.RELEASE Fixed IGNITE-6879 Migrated to spring-data 2.0.5.RELEASE Migrated to spring 5.0.4.RELEASE Fixed overrided methods naming You

Re: IEP-14: Ignite failures handling (Discussion)

You are suggesting to kill the process, which was not started by Ignite, are not you? More consistently is to stop only those processes that are generated by the control of Ignite, e.g. from ignite.sh - here it is ok for me. If we relese 'kill by default' as part of 2.5, we will end up with 2.6

Re: IEP-14: Ignite failures handling (Discussion)

Dmitriy, I think everyone is suggesting that stopping the node will likely be impossible if Ignite is frozen. Moreover, it is very likely that all other apps are frozen too. My comments are below... On Tue, Mar 13, 2018 at 9:12 AM, Dmitry Pavlov wrote: > Please consider

Re: Apache Ignite nightly release builds

We can start with this approach. And if we will need some staging maven repo, we can support it later. вт, 13 мар. 2018 г. в 18:08, Dmitriy Setrakyan : > Huge +1. > > Any idea about how much effort this involves? > > D. > > On Tue, Mar 13, 2018 at 11:05 AM, vveider

Re: Apache Ignite nightly release builds

Not mush I presume, at least for woking prototype. As I mentioned before — there is fully operational Release Build, which can be used as example for nightly builds. > On 13 Mar 2018, at 18:07, Dmitriy Setrakyan wrote: > > Huge +1. > > Any idea about how much effort

Re: Apache Ignite nightly release builds

Huge +1. Any idea about how much effort this involves? D. On Tue, Mar 13, 2018 at 11:05 AM, vveider wrote: > Hi, Igniters! > > > I suggest we continue our discussion concerning Apache Ignite nightly > release builds. > > I'd like to prepare one on our CI server (TeamCity)

Apache Ignite nightly release builds

Hi, Igniters! I suggest we continue our discussion concerning Apache Ignite nightly release builds. I'd like to prepare one on our CI server (TeamCity) and will be glad to hear wishes and proposal about this project. Currently, I see it as scheduled build which builds release binaries from

[jira] [Created] (IGNITE-7937) Move Apache Ignite 2.4+ Java 8 tests to Single Build architecture

Peter Ivanov created IGNITE-7937: Summary: Move Apache Ignite 2.4+ Java 8 tests to Single Build architecture Key: IGNITE-7937 URL: https://issues.apache.org/jira/browse/IGNITE-7937 Project: Ignite

[jira] [Created] (IGNITE-7936) Make partition state transfer from OWNING state possible only within exchange.

Ilya Lantukh created IGNITE-7936: Summary: Make partition state transfer from OWNING state possible only within exchange. Key: IGNITE-7936 URL: https://issues.apache.org/jira/browse/IGNITE-7936

[jira] [Created] (IGNITE-7934) Do not checkpoint pages from MOVING partitions

Ilya Lantukh created IGNITE-7934: Summary: Do not checkpoint pages from MOVING partitions Key: IGNITE-7934 URL: https://issues.apache.org/jira/browse/IGNITE-7934 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7935) Add batch put operation to B+ tree implementation.

Ilya Lantukh created IGNITE-7935: Summary: Add batch put operation to B+ tree implementation. Key: IGNITE-7935 URL: https://issues.apache.org/jira/browse/IGNITE-7935 Project: Ignite Issue

Apache Ignite community in social network VK.com

Hi! We created https://vk.com/apacheignite for Russian speaking community. That will be the hub for Apache Ignite events and resources in Russian. Follow the group to get latest news and suggest activities for Moscow, Petersburg or other cities. Привет! Мы создали https://vk.com/apacheignite для

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

Absolutely agree. Personally I find it particularly frustrating, that *IgniteConfiguration.networkTimeout* and TcpDiscoverySpi.networkTime*out *are not the same thing. If we had a small set of timeouts with simple and clear semantics, it would make everybody happier. Denis вт, 6 мар. 2018 г. в

[GitHub] ignite pull request #3481: IGNITE-7638: Page replacement process in PDS mode...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3481 ---

[GitHub] ignite pull request #3627: IGNITE-7932: Add example for Linear SVM with Iris...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3627 IGNITE-7932: Add example for Linear SVM with Iris Dataset You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7932

Re: Deploying 2.4 artifacts to maven repo

Thank you for noticing that. Vladimir, is it expected for current release stage? Sincerely, Dmitriy Pavlov вт, 13 мар. 2018 г. в 15:34, aaksenov : > hello, it seems that 2.4 jars are missing in maven central >

Re: IEP-14: Ignite failures handling (Discussion)

Please consider that user application may use Ignite as optional cache for some low-priority feature, but main logic is well functioning without Ingnite. I can say, as Ignite user in the past, that it is quite real case. Second real case is using several war files within one application server,

[jira] [Created] (IGNITE-7933) The error writing wal point to cp/node-start file can lead to the inability to start node

Dmitriy Govorukhin created IGNITE-7933: -- Summary: The error writing wal point to cp/node-start file can lead to the inability to start node Key: IGNITE-7933 URL:

Re: Data eviction/expiration from Ignite persistence

Dmitriy, The TTL map is a regular B+Tree-based map with the key being a pair (expire time + key). It is obviously stored in memory when there is no persistence. When persistence is enabled, it is handled as any other index tree - the page replacement algorithm is applied. No heap is consumed for

[GitHub] ignite pull request #3571: IGNITE-7531: Implemented copy, insert, batched in...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3571 ---

[jira] [Created] (IGNITE-7932) [ML] Adopt SVM Linear Binary Classification Example to the new Partitioned Dataset

Aleksey Zinoviev created IGNITE-7932: Summary: [ML] Adopt SVM Linear Binary Classification Example to the new Partitioned Dataset Key: IGNITE-7932 URL: https://issues.apache.org/jira/browse/IGNITE-7932

Deploying 2.4 artifacts to maven repo

hello, it seems that 2.4 jars are missing in maven central https://mvnrepository.com/artifact/org.apache.ignite/ignite-core but the version has been released. could you please upload them? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #3626: IGNITE-7898 Fixed IgniteCachePartitionLossPolicy ...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3626 IGNITE-7898 Fixed IgniteCachePartitionLossPolicy tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7898

Re: Data eviction/expiration from Ignite persistence

On Tue, Mar 13, 2018 at 3:50 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Denis, > > What do you mean by 'current behavior when data is evicted from the memory > only'? TTL expiration effectively means that the corresponding key-value > pairs are destroyed. AG, can you please

Re: IEP-14: Ignite failures handling (Discussion)

On Tue, Mar 13, 2018 at 8:16 AM, Dmitry Pavlov wrote: > Dmitriy, alternative is "kill if standalone, stop if embedded" > User will be still able to set something like > -DNODE_CRASH_ACTION="kill" > if ignite.sh is not used and user accepts alternative that whole process

Re: IEP-14: Ignite failures handling (Discussion)

The most doubtful thing is 'stopping'. What if node does not respond due to critical failure? 2018-03-13 15:16 GMT+03:00 Dmitry Pavlov : > Dmitriy, alternative is "kill if standalone, stop if embedded" > > User will be still able to set something like >

Re: MAC addresses emulation in Testing Framework

Sure, agree here that static/final and reflection update is not best practice. вт, 13 мар. 2018 г. в 11:26, Vyacheslav Daradur : > Dmitry, I've changed a logic of my tests and reflection isn't needed > anymore. > > Using reflection in tests, especially on 'private static |

Re: IEP-14: Ignite failures handling (Discussion)

Dmitriy, alternative is "kill if standalone, stop if embedded" User will be still able to set something like -DNODE_CRASH_ACTION="kill" if ignite.sh is not used and user accepts alternative that whole process would be killed if node is crashed. Default would be 'node stop', but not hang up

Re: Data eviction/expiration from Ignite persistence

Hi Denis, I've created summary of terms here https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood#IgniteDurableMemory-underthehood-Eviction,rotationandexpiration Hope this should solve a lot of miscommunications. In this thread I meant only Expiration (aka

Re: IEP-14: Ignite failures handling (Discussion)

Guys, I do not understand the alternative. If Ignite is frozen and causes the whole grid to freeze, how can we justify not killing it? Will uses rather have their applications freeze? I would consider real life use cases here. Can someone present a life example where keeping a frozen grid node

[GitHub] ignite pull request #3625: Ignite wc 157

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/3625 Ignite wc 157 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-wc-157 Alternatively you can review and apply

[jira] [Created] (IGNITE-7931) Wrong arguments for `keys` in DataStreamerImpl

Ivan Fedotov created IGNITE-7931: Summary: Wrong arguments for `keys` in DataStreamerImpl Key: IGNITE-7931 URL: https://issues.apache.org/jira/browse/IGNITE-7931 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7930) Partition map hang in incorrect state when backup filter is assigned

Vladislav Pyatkov created IGNITE-7930: - Summary: Partition map hang in incorrect state when backup filter is assigned Key: IGNITE-7930 URL: https://issues.apache.org/jira/browse/IGNITE-7930

Re: IEP-14: Ignite failures handling (Discussion)

I also like "kill if standalone, stop if embedded" by default. A use can change it to kill for embedded mode, but it will be a controlled safe choice. 2018-03-13 11:26 GMT+03:00 Vladimir Ozerov : > +1 for "kill if standalone, stop if embedded". We should never kill a >

[GitHub] ignite pull request #3600: IGNITE-7860 JDBC thin driver: set default socket ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3600 ---

[jira] [Created] (IGNITE-7929) Web console: error frame too long on sign in

Pavel Konstantinov created IGNITE-7929: -- Summary: Web console: error frame too long on sign in Key: IGNITE-7929 URL: https://issues.apache.org/jira/browse/IGNITE-7929 Project: Ignite

[jira] [Created] (IGNITE-7928) Exception is not propagated to the C# client and the app hangs

Evgenii Zhuravlev created IGNITE-7928: - Summary: Exception is not propagated to the C# client and the app hangs Key: IGNITE-7928 URL: https://issues.apache.org/jira/browse/IGNITE-7928 Project:

Re: IEP-14: Ignite failures handling (Discussion)

+1 for "kill if standalone, stop if embedded". We should never kill a process in embedded node because it might be disastrous for user application. On Tue, Mar 13, 2018 at 10:41 AM, Dmitry Pavlov wrote: > Denis, Dmitriy, I am not sure I agree here, please see close

Re: MAC addresses emulation in Testing Framework

Dmitry, I've changed a logic of my tests and reflection isn't needed anymore. Using reflection in tests, especially on 'private static | final' fields may provide side-effects on other tests in a common test suite which will be started in same JVM because of a previous value that may be cached in

Re: MD5 sums in the releases

Hi Cos, Thank you for noticing it. As ASF veteran, could you please confirm that it is valid to remove MD5 from already published release? I am in doubts because it means that we voted on one fileset and released another. Is it Ok from ASF perspective? Vladimir. On Mon, Mar 12, 2018 at 9:16 PM,

Re: Data eviction/expiration from Ignite persistence

Denis, What do you mean by 'current behavior when data is evicted from the memory only'? TTL expiration effectively means that the corresponding key-value pairs are destroyed. If you are talking about page replacement, then there is no way to do this on per-key basis because a page must be

Re: IEP-14: Ignite failures handling (Discussion)

Denis, Dmitriy, I am not sure I agree here, please see close analogue - JVM itself, and its parameter ExitOnOutOfMemoryError,- it is not default. If server node is started from sh script, kill OK for me, as process is controlled only by ignite. It is sufficient to add option to override default

Re: IGNITE-5357 is ready for review (Replicated cache reads load balancing)

Dmitry, Nickolay accepted PR changes at Upsource [1]. Latest ci.build [2] looks good in comparison with master [3]. Following tests passed locally: CacheAffinityCallSelfTest.testAffinityCallFromClientRestartNode CacheAffinityCallSelfTest.testAffinityCallRestartNode

Re: [RESULT] [VOTE] Apache Ignite 2.4.0 Release (RC1)

There is an error in RPM documentation on site — missing header for ignite.repo file and formatting is also wrong. Otherwise — I’m able to install and run Apache Ignite from RPM from ASF according to manual. > On 12 Mar 2018, at 23:25, Denis Magda wrote: > > Released RPM