Re: Data vanished from cluster after INACTIVE/ACTIVE switch

2020-02-03 Thread Alexei Scherbakov
Alexey Goncharuk, I see no issues with "lost" partitions. The same is possible right now in persistence mode. Node can be killed and data erased while grid is deactivated. After re-join it should rebalance itself from existing owners (if any exists). вт, 4 февр. 2020 г. в 10:54, Alexei

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

2020-02-03 Thread Alexei Scherbakov
Folks, For a long time we have a flag [1] It does almost what we want here. I suggest to make this behavior default and rework it to keep data in memory as well (we already have special "recovery" mode for caches). [1] org.apache.ignite.IgniteSystemProperties#IGNITE_REUSE_MEMORY_ON_DEACTIVATE

[jira] [Created] (IGNITE-12618) Affinity cache for version of last server event can be wiped from history

2020-02-03 Thread Vyacheslav Koptilin (Jira)
Vyacheslav Koptilin created IGNITE-12618: Summary: Affinity cache for version of last server event can be wiped from history Key: IGNITE-12618 URL: https://issues.apache.org/jira/browse/IGNITE-12618

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

2020-02-03 Thread Alexey Goncharuk
I do not mind making this change if we explicitly and clearly define what 'new inactive state' means. What should happen if a partition is lost in inactive state? What if such node joins back the cluster after? Etc. пт, 31 янв. 2020 г. в 20:57, Denis Magda : > Back up Ivan's opinion here.

[jira] [Created] (IGNITE-12617) PME-free switch should wait for recovery only at affected nodes.

2020-02-03 Thread Anton Vinogradov (Jira)
Anton Vinogradov created IGNITE-12617: - Summary: PME-free switch should wait for recovery only at affected nodes. Key: IGNITE-12617 URL: https://issues.apache.org/jira/browse/IGNITE-12617

Re: Internal classes are exposed in public API

2020-02-03 Thread Andrey Gura
Just post here article from Oracle documentation "How and When To Deprecate APIs" [1]. [1] https://docs.oracle.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation.html On Fri, Jan 31, 2020 at 10:44 AM Pavel Tupitsyn wrote: > > Agree with Andrey, let's remove deprecation for now

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2020-02-03 Thread Maxim Muzafarov
Igniters, Let me share the current status of the release. 1. Waiting for the issues [1] [2] (discussed previously this thread) to be tested by TC.Bot and merged to the 2.8 release branch. 2. Only 2 release BLOCKER issues left. I'm planning to move these issues to 2.8.1 release. The issue [4]

Re: Move Spring Data modules into Ignite extension project

2020-02-03 Thread Ilya Kasnacheev
Hello! Since Spring Data integration is actively used (compared to most others), I would argue that it should only moved to extensions last, when this process is debugged thoroughly and when we have at least one "essentials + extensions" release shipped with feedback. I think such release would