Re: Data vanished from cluster after INACTIVE/ACTIVE switch

[Vladimir Steshin]

>
> Hi,  Vyacheslav.
>
>
>
> >>> In general, it is a caching layer above an existing 3rd party database.
> That is all.
> >>> I don't think so. It does not really matter which persistence is used
> (Ignite native persistence or RDBMS).
>
>
>
> Ok. I think we might also check if read/write-through is enabled for a
> cache to consider it as persistent and not to warn user, not to require
> ‘force’ flag.
>
>
>
>
>
> >>> it does make sense to me (control utility and jmx) To be honest, I
> don't
> see a reason to introduce this flag into Java API.
>
>
>
> The only reason is the same implementation IgniteMXBean#active(boolean)
> and Ignite#active(boolean). Looks like we have to choose whether to allow
> user erase data unexpectedly or to change behavior of the API call.
>