Hello,
We run into the problem migrating from Ignite version 2.8.1 to 2.11.0
If the authentication is enabled the ignite service which is deployed at
node startup prevents it from starting with the 'Security context isn't
certain' exception.
We have prepared a simple test reproducing the problem
Hello,
We have a trouble migrating the persistent data from the Ignite 2.8.1 to
2.11.0. The native persistence is used and one the caches has an
CacheInterceptor configured.
If we run Ignite 2.11.0 against the persistent data created in 2.8.1
nodes do not start (only the 1st node starts but all o
gnite.cluster().state(ClusterState.ACTIVE);
>
> ignite.services().deploy(serviceConfiguration);
>
> чт, 18 нояб. 2021 г. в 07:39, Sergey Korotkov
> mailto:serge.korot...@gmail.com>>:
>
> Hello,
>
> We run into the problem migrating from Ignite ve
Hello,
Are there any comments on the issue? Is it a bug? Or may be the
expected behaviour and known incompatibility?
Thanks,
- -
Sergey
18.11.2021 17:37, Sergey Korotkov пишет:
> Hello,
>
> We have a trouble migrating the persistent data from the Ignite 2.8.1 to
> 2.11.0
ned twice, not during expiration cleanup, but also
>> during rebalance eviction. But your scenario looks quite usual
>> and couldn't cause such problems.
>>
>> I've found similar existing
>> ticket https://issues.
> <https://issues.apache.org/jira/browse/IGNITE-14252>
>
> Denis Chudov
> Software Engineer, Moscow
> +7 905 5775239
> https://www.gridgain.com <https://www.gridgain.com/>
> Powered by Apache® Ignite™
>
>
> On Tue, Nov 23, 2021 at 8:32 AM Sergey Korotkov
>
Hi,
Does it still fail if wait all futures returned from the putAsync calls
before exiting the writer app?
Thanks,
--
Sergey
On 7/28/25 13:26, Michael Karmazin wrote:
Hi, I’m contracting (via Algoteq I'm writing from here) for a Fortune
500 financial institution with a global footprint. I
