[no subject]

2021-11-23 Thread vtchernyi
Hi community,I try to remember how to set non default partition number for some cache. Do we have java/xml example at ignite.apache.org website?Vladimir

Re:

2021-11-23 Thread andrei
Hi, You can set it as part of CacheConfiguration: https://www.javadoc.io/doc/org.apache.ignite/ignite-core/1.6.0/org/apache/ignite/configuration/CacheConfiguration.html#setAffinity(org.apache.ignite.cache.affinity.AffinityFunction) Regards, Andei 11/23/2021 1:39 PM, vtch

rendezvous partitions on the web

2021-11-23 Thread Vladimir Tchernyi
Thanks, I'd fount that already in my recent project repo. The question is about the website, I did not manage to find that info there. "how to set non default partition number for some cache" - do we have java/xml example at ignite.apache.org website? Vladimir PS: sorry for missing thread name,

Re: Affinity function with thin clients

2021-11-23 Thread R. Subhash Babu
Thnk you Stephen and Pavel. Seems like I have to go with a thick client for my use case. On Mon, Nov 22, 2021, 8:35 PM Pavel Tupitsyn wrote: > You can use define one or more cache templates [1] with a custom affinity > function (or any other setting) on the server side, > then create caches usin

[Ignite Summit: Cloud Edition] Results and thanks

2021-11-23 Thread Kseniya Romanova
Hi Igniters! 9 speakers, 5 hours, attendees from 44 countries—the Ignite Summit: Cloud Edition was quite a warm and successful community gathering! A big thanks to all our wonderful speakers and the summit team (including the Program Committee members): Nikita Ivanov Shahir Daya Alain Guigui St

Re: [2.11.0]: 'B+Tree is corrupted' exception in GridCacheTtlManager.expire() and PartitionsEvictManager$PartitionEvictionTask.run() on node start

2021-11-23 Thread Denis Chudov
Hi Sergey! Thank you for providing details. Have I understood correctly that you run newer version of Ignite on older persistent files? Is there any possibility that some data in your caches survived that 5 days of cluster work? I'm just trying to exclude any compatibility problems, like https://i