Re: Ignite Segmentation Behaviour

Hi, Thank's for the clarificaiton! That's what I expected. I looked into https://github.com/luqmanahmad/ignite-plugins and decided to implement my own SegmentationResolver to deal with these cases. Cheers Sam -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Getting NullPointerException during commit into cassandra, after reconnecting to ignite server

I got this exception for ignite 2.8.0. When the note restarted and the data is inserted into the cache and Cassandra store. Please note 1) my setup is that Native Persistence is enabled. just one server node, no client node 2) there is no issue for the very first start (i.e. the native storage

Re: backup

Hi, Ignite is in the process of developing backup/snapshots capability see: https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteSnapshot.java and: https://cwiki.apache.org/confluence/display/IGNITE/IEP-43%3A+Cluster+snapshots also checkout: https://w

Re: Ignite 3.0 meetups

Hi, igniters! Thanks to all who attended today's event, that was a really warm community gathering even though we met online! And thanks to Val for his presentation. I hope these materials will help to run the discussion about Ignite 3.0[1] Video: https://youtu.be/zPuLJgUfLaM Slides with all links:

backup

hi all Is it possible to backup/restore cache content across ignite clusters? If not, how do I minimize data loss in case of an ignite cluster crash? I am already backing up the native persistence. thanks.

Re: Tech talk: thoughts and suggestions on how to use Ignite with serverless functions

Pavel, thanks for catching that. These are the correct coordinates of the tutorial . - Denis On Tue, Sep 15, 2020 at 10:21 AM Pavel Tupitsyn wrote: > Hi Denis, > > The tutorial link leads to Martin's website > > On T

Tech talk: thoughts and suggestions on how to use Ignite with serverless functions

Igniters, The serverless architecture is getting more traction these days since it helps us to reduce the costs of our cloud-based applications. Several months ago I decided to research if Ignite is 100% ready for serverless dep

Re: Lag before records are visible after transaction commit

Hello! I think this suggests data model adjustment. Regards, -- Ilya Kasnacheev вт, 15 сент. 2020 г. в 17:46, Evgenii Zhuravlev : > Ilya, > > This won't help, since the problem here is that CQ doesn't return all > needed keys. > > Evgenii > > вт, 15 сент. 2020 г. в 02:28, Ilya Kasnacheev : >

Re: Lag before records are visible after transaction commit

Ilya, This won't help, since the problem here is that CQ doesn't return all needed keys. Evgenii вт, 15 сент. 2020 г. в 02:28, Ilya Kasnacheev : > Hello! > > Maybe keys may be queued from the CQ to be revisited later with > transaction per key approach. > > Regards, > -- > Ilya Kasnacheev > > >

Re: Ignite Segmentation Behaviour

Hello! After all, it is only you who can decide whether your cluster has segmented or not. The traditional solution is "the largest one wins", but if the parts of cluster can't communicate, it becomes undecidable. Regards, -- Ilya Kasnacheev пн, 14 сент. 2020 г. в 12:01, sue : > Hi Denis, > >

Re: Ignite client node raises "Sequence was removed from cache" after Ignite Server node restarts

Hello! You need to do this outside of your transaction. Regards, Ilya. -- Ilya Kasnacheev сб, 12 сент. 2020 г. в 02:42, xmw45688 : > Hi Ilya, > > Tried your suggestion, removing the userSeq field from the class. It still > raise the same exception - > org.apache.ignite.IgniteException: C

Re: How to persist data only on selected nodes but not all nodes in cluster

Hello! Do you have a reproducer which highlights the issue? Having said that, I don't really recommend having long-lived nodes outside BLT. Maybe it was expected to be a supported scenario, but I doubt it is tested very much. Nowadays it is assumed that all non-BLT nodes get added after baseline

Re: Issue in Alter Table - Drop Column functionality

Hello! I have just validated it on 2.8.1. Seems to work! ~/Downloads/apache-ignite-2.8.1-bin% bin/sqlline.sh sqlline version 1.3.0 sqlline> !connect jdbc:ignite:cfg://config/default-config.xml [12:33:33]__ [12:33:33] / _/ ___/ |/ / _/_ __/ __/ [12:33:33] _/ //

Re: Lag before records are visible after transaction commit

Hello! Maybe keys may be queued from the CQ to be revisited later with transaction per key approach. Regards, -- Ilya Kasnacheev пн, 14 сент. 2020 г. в 21:15, Evgenii Zhuravlev : > No, I don't see other ways to do this transactionally, as CQ itself is not > transactional. > > Evgenii > > чт,