Re: Ignite 2.16 entry processors sometimes execute twice

Hi Raymond, Besides the answer Pavel provided, please take into account that entry processor implementation should avoid generating random values for the entry being updated. For example, mutableEntry.setValue(rand.nextInt()) might lead to data inconsistency. * * An instance of entry processor

Re: Ignite TryGet - cache data not found intermittently

class="org.apache.ignite.configuration.DataStorageConfiguration"> > > class="org.apache.ignite.configuration.DataRegionConfiguration"> > value="Common_Dynamic_Data_Region"/> >

Re: Ignite TryGet - cache data not found intermittently

пн, 10 июн. 2024 г. в 14:22, Вячеслав Коптилин : > Hello Charlin, > > Could you share your cache configuration? Specifically, what values are > used for `readFromBackup` and `writeSynchronizationMode`. > > Thanks, > S. > > ср, 5 июн. 2024 г. в 15:49, Charlin S : > >

Re: Ignite TryGet - cache data not found intermittently

Hello Charlin, Could you share your cache configuration? Specifically, what values are used for `readFromBackup` and `writeSynchronizationMode`. Thanks, S. ср, 5 июн. 2024 г. в 15:49, Charlin S : > Hi All, > I am unable to fetch data from cache by reading by > key.intermittently (very rarely).

Re: Does SQL Query support TouchedExpiryPolicy?

Hello, Unfortunately, SQL does not support TouchedExpiryPolicy. You need to use KeyValue API to get benefits from it. Thanks, S. пт, 15 дек. 2023 г. в 04:56, 38797715 <38797...@qq.com>: > From javadoc, An ExpiryPolicy that defines the expiry Duration of a Cache > Entry based on when it was

Re: Will ScanQuery scan intermediate data for pessimistic transactions?

Hello, Yes, scan queries do not honor transaction guarantees. Thanks, S. ср, 27 дек. 2023 г. в 14:43, 38797715 <38797...@qq.com>: > Hi, > > The demo is as follows and attached, It seems that ScanQuery has read the > intermediate data of the transaction. > > Execute the following code: > @Slf4j

Re: incompatible class error

Hello, In general, you need to provide the right version of JCache API on all nodes. Please take a look at https://issues.apache.org/jira/browse/IGNITE-11986 (The issue mentioned in the ticket looks very similar to your case) Thanks, S. пн, 15 мая 2023 г. в 21:00, Jiang Jacky : > Hello, can

Re: JmxExporter error while starting ignite node

Hello Abhishek, You don't need to register JmxSystemViewExporterSpi explicitly via configuration. This exporter implicitly enabled/registered on the startup Ignite node. That is the reason why you are getting: IgniteCheckedException: Duplicate SPI name (need to explicitly configure 'setName()'

Re: REST API TIMESTAMP

Hello, I'll just duplicate the answer from https://stackoverflow.com/questions/73703680/apache-ignite-rest-api-timestamp-format (Thanks to Igor Belyakov!) The issue is related to the default locale provider change in the Java 9+, see JEP 252 . As a workaround, you

Re: partitionLossPolicy confused

Hello, In general there are two possible ways to handle lost partitions for a cluster that uses Ignite Native Persistence: 1. - Return all failed nodes to baseline topology. - Call resetLostPartitions 2. - Stop all remaining nodes in the cluster. - Start all nodes in the cluster

Re: Node crashed with error "Getting affinity for too old topology version that is already out of history"

Hello Marcus, It looks like a bug. I will check and file a jira issue. > I suppose Ignite should be fault tolerant and outage of some nodes should not cause shutdown of other nodes. You are absolutely right. Thanks, S. ср, 6 апр. 2022 г. в 10:49, Lo, Marcus : > Hi Ignite team, > > > > Can

Re: Blocked system-critical due to a listener?

Hello Joan, > What I've done is launch an async worker from the listener to do that operation. Yep, that is true. Event listeners can be called from Ignite internal threads (which can be critical ones). I think it was done this way for performance reasons. At least, this allows you to avoid

Re: getOrCreateCache hangs when cacheStore uses spring resources

Hello, Could you please share log files and a full thread dump from the node? Thanks, S. чт, 27 мая 2021 г. в 14:20, Orange : > Calling ignite.getOrCreateCache(cacheConfig) results in the thread getting > blocked. I've noticed this does not happen when the cacheStore does not use > spring

Re: data rebalancing and partition map exchange with persistence

Hi Alan, I am sorry for the typo in your name, it was done unintentionally. Thanks, S. чт, 4 февр. 2021 г. в 19:10, Вячеслав Коптилин : > Hello Allan, > > > Does data rebalancing occur when a node leaves or joins, or only when > you manually change the baseline topology (ass

Re: data rebalancing and partition map exchange with persistence

Hello Allan, > Does data rebalancing occur when a node leaves or joins, or only when you manually change the baseline topology (assuming automatic baseline adjustment is disabled)? Again, this is on a cluster with persistence enabled. Yes, this can happen when a node joins the cluster, for

Re: PME and affinity guarantees

Hello Ivan, Well, EVT_CACHE_REBALANCE_PART_LOADED is triggered when the corresponding partition is fully rebalanced and moved into the "OWNING" state, and so, invoking Affinity#isPrimaryOrBackup(ignite.cluster().localNode(), key) on this node should return "true". to be more precise, this

Re: Apache Ignite Clientside NearCache and Serverside Eviction blocking cluster

Hello Prasad, Sorry for the late reply. I checked your reproducer and it looks good to me. And yes, this behavior looks like a bug. I filed a Jira ticket in order to address this issue: https://issues.apache.org/jira/browse/IGNITE-13858 You can enable ignite native persistence in order to

Re: Apache Ignite Clientside NearCache and Serverside Eviction blocking cluster

Hello Prasad, I will take a look and file a ticket if needed. Thanks, S. пн, 23 нояб. 2020 г. в 19:23, pvprsd : > Hi, > > Did anyone get a chance to look into this issue? Is this supported > configuration for ignite? As these 2 (clientside NearCache and serverside > eviction) are very common

Re: Ignite client node hangs while IgniteAtomicLong is created

Hello Ilya, I have a look at your logs and thread dumps. This definitely a bug. The data structure processor does not properly initialize when a client node connects to a cluster that changes its own state (state transition from the inactive state to active). I have created a ticket in order to

Re: Data is lost during rebalance

Hi Alex, I will take a look at log files. Thanks, S. ср, 6 нояб. 2019 г. в 17:51, novacean.alex : > This is the test i am performing: > > 1. I have an Ignite Cluster of 3 Server Nodes running in Kubernetes. (the > cluster is created using a StatefulSet) > 2. Once the cluster is up i use a

Re: Data is lost during rebalance

We are definitely missing something obvious. ))) 1. Let's check log files for the following message: "Page-based evictions started. Consider increasing 'maxSize' on Data Region configuration:" 2. Please try to disable page eviction for the default data region. 3. Could you please describe your

Re: Data is lost during rebalance

Hi Alex, Oh... I missed the fact that your cache is replicated. In that case, you don't need to specify the number of backups. Could you please check, that the cache mode is replicated? You can try the following code snippet:

Re: Data is lost during rebalance

Hello Alex, You need to specify the number of backups for your cache. For instance, ... ... Please take a look at the page for details: https://apacheignite.readme.io/docs/primary-and-backup-copies Thanks, S. ср, 6

Re: Ignite 2.7.0 : server node: null pointer exception

Hi Mahesh, Yes, it should be done on server nodes. Thanks, S. чт, 25 июл. 2019 г. в 14:28, Mahesh Renduchintala < mahesh.renduchint...@aline-consulting.com>: > IGNITE_DISCOVERY_HISTORY_SIZE=700 > > Does this go on the server side or the thick client side ? > >

Re: Ignite 2.7.0 : server node: null pointer exception

Hi Mahesh, It definitely looks like a bug. I have created this ticket in order to track the issue https://issues.apache.org/jira/browse/IGNITE-12013 As a temporary workaround, I would propose increasing discovery history size

Re: Apache Ignite expired data remains in memory with TTL enabled and after thread execution

Hello, It seems this is a known issue https://issues.apache.org/jira/browse/IGNITE-11438 which was recently fixed and will be available in AI 2.8. Thanks, S. пн, 22 июл. 2019 г. в 15:02, ales : > Hello, > > Our company is currently facing an issue with Ignite expired entries that > remains in

Re: Ignite node crash: IndexOutOfBoundsException

Hi Mahesh, It looks like a known issue https://issues.apache.org/jira/browse/IGNITE-8552 Anyway, could you please share your cache configuration? Thanks, S сб, 20 июл. 2019 г. в 06:41, Mahesh Renduchintala < mahesh.renduchint...@aline-consulting.com>: > Hi > > > We have an

Re: unsubscribe

Hi, Hello, To unsubscribe from the user mailing list send an e-mail to user-unsubscribe @ignite.apache.org If you have a mailing client, follow the unsubscribe link here: https://ignite.apache.org/community/resources.html#mail-lists Thanks, S. пт, 12 июл. 2019 г. в 23:26, Majid Salimi : >

Re: Memory leak.Ignite runs slower and slower after a period of time.

Hi, > Does it mean the cursor still not closed in Ignite-2.6.0? Yes, it seems so. Thanks, S. чт, 11 апр. 2019 г. в 15:06, Justin Ji : > Emmm, Does it mean the cursor still not closed in Ignite-2.6.0? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Memory leak.Ignite runs slower and slower after a period of time.

Hi, > BTW, I can not find the class you provided(Ignite-2.6.0), do you spell it correctly? Oops :) That class was added recently. Please take a look at https://issues.apache.org/jira/browse/IGNITE-10827 The fix is already available on the master branch Thanks, S. чт, 11 апр. 2019 г. в 14:10,

Re: Memory leak.Ignite runs slower and slower after a period of time.

Hello, > I would like to know will resource be closed after I iterate over the Cursor? Well, the answer is yes, the cursor will be closed (the underlying iterator is wrapped by org.apache.ignite.internal.processors.cache.AutoClosableCursorIterator). Please take into account that this behavior is

Re: Memory leak.Ignite runs slower and slower after a period of time.

Hello, At first glance, your code does not close FieldsQueryCursor instances. Could you explicitly close the cursors via close() or use try-with-resources statement. [1] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/FieldsQueryCursor.html [2]

Re: no data by JDBC or Cache query!

Hi, Please make sure that your types are registered as follows: CacheConfiguration ccfg = new CacheConfiguration<>("PersonCache"); ccfg.*setIndexedTypes*(String.class, Person.class); ... IgniteCache personCache = igniteClient.getOrCreateCache(ccfg); additional details can be

Re: Cassandra writeBehind configuration

Hello, It looks like a known issue https://issues.apache.org/jira/browse/IGNITE-8788. Unfortunately, it is not resolved yet. I would suggest the following workaround: 1. create your own CacheStoreFactory public class CustomCassandraCacheStoreFactory extends CassandraCacheStoreFactory {

Re: Default Cache template

Thanks for catching that. I already proposed the fix of xml example. I hope the doc will be updated soon. Regards, S. ср, 30 янв. 2019 г. в 22:30, mahesh76private : > It works. > > it isn't in your documentation though. > https://apacheignite.readme.io/docs/cache-template > > > > > -- > Sent

Re: Default Cache template

Hello, You have to add '*' to the cache name as follows: Thanks, S. вт, 29 янв. 2019 г. в 11:07, mahesh76private : > Hi, > > I added the below, in node config.xml file. However, SQL table create from > client side keep

Re: Limiting the number of files in WalArchive folder

Hello, The size of WAL Archive is controlled by the 'DataStorageConfiguration#walHistorySize' property [1], which is 20 checkpoints by default [2]. As of Apache Ignite 2.7, you can specify the size of wal archive in bytes via 'DataStorageConfiguration#setMaxWalArchiveSize()' method [3]. [1]

Re: Do I need CacheStoreFactory class and hibernate configuration on Remote Node?

Hello, > Do I need CacheStoreFactory class and hibernate configuration on Remote Node? Yes, CacheStore classes must be in the classpath on all nodes (including the client nodes) For example, you can put them to '$IGNITE_HOME/libs' folder (a subfolder can be created for convenience as well). >

Re: Ignite Cluster: Cache Misses happening for existing keys

tually calling some backend legacy API and the caching layer is setup > to reduce the load for it. > > > > *From:* Вячеслав Коптилин [mailto:slava.kopti...@gmail.com] > *Sent:* Thursday, September 13, 2018 4:08 AM > *To:* user@ignite.apache.org > *Subject:* Re: Ignit

Re: Ignite Cluster: Cache Misses happening for existing keys

Hello, Your code contains the following obvious race: String value = *cache*.get(key); *if *(value == *null*) { *cache*.put(key, *getNewValue*()); *LOG*.info(*"Cache put key={} "*, key); } It's easy to imagine that two threads managed to execute get() method and got

Re: Partition map exchange in detail

Hello Eugene, I hope you meant PME (partitions map exchange) instead of NPE :) > What constitutes a transaction in this context? If I am not mistaken, it is about Ignite transactions. Please take a look at this page https://apacheignite.readme.io/docs/transactions > Does it mean that if the

Re: How to create tables with JDBC, read with ODBC?

Hi, > I have tried various things on the Java side to make the Public schema explicit, such as this: If I'm not mistaken the schema can be specified as a parameter of ODBC connection string. Please take a look at this page:

Re: configuration for some persistent and some non-persistent caches

I meant `datastore` cache of course ) Thanks, S. ср, 5 сент. 2018 г. в 19:04, Вячеслав Коптилин : > Hello, > > I just tried the configuration, you provided, and it works as expected. > I mean that only `datasource` cache persists its own data. > Please make sure you clean up wo

Re: configuration for some persistent and some non-persistent caches

Hello, I just tried the configuration, you provided, and it works as expected. I mean that only `datasource` cache persists its own data. Please make sure you clean up working directory before testing. Thanks, S. вс, 2 сент. 2018 г. в 11:50, joseheitor : > Hi Denis, > > I am struggling to get

Re: error starting Ignite -Failed to activate node components

Hello, The root cause of the issue is that your Spring configuration is not quite correct. It seems that the `dataSource` property [1] refers to the `dsSQLServer_Sustainanalytics` which cannot be found: Caused by: class org.apache.ignite.IgniteCheckedException: Spring bean with the provided

Re: How to check if key exists in DataStreamer buffer so that it can be flushed?

at we do is have a version # that we store in the value, and the > StreamReceiver ignores earlier versions. > -DH > > On Wed, Aug 29, 2018 at 8:08 AM, Вячеслав Коптилин < > slava.kopti...@gmail.com> wrote: > >> Hello, >> >> I don't think there is a way to

Re: How to check if key exists in DataStreamer buffer so that it can be flushed?

Hello, I don't think there is a way to do that check. Moreover, it seems to me that is useless in any case. The thing that allows you to achieve the desired behavior is `allowOverwrite` flag [1]. By default, the data streamer will not overwrite existing data, which means that if it will encounter

Re: How many threads does ignite.executorService() have.

Hello, Usually, the size of a thread pool is max(8, total number of CPU's). The details about configuration particular thread pools can be found here: https://apacheignite.readme.io/docs/thread-pools Thanks, S. вт, 28 авг. 2018 г. в 15:49, begineer : > Hi Guys, > I have one simple query about

Re: While enabling JCache, JCacheMetrics is throwing NullPointerException in getCacheManager with spring boot

Hello, As I mentioned above, this exception indicates that the cache with the given name already exists in the cluster. Thanks, S. пт, 17 авг. 2018 г., 10:52 daya airody : > Hi Slava, > > other reply is about issues in caching Spring proxied objects. > > I am also seeing "Cache already

Re: sql query log

Hello, If I am not mistaken, there is no such capability out of the box. You can try to use IgniteConfiguration#longQueryWarningTimeout property as a workaround. For example, you can set this property to 1ms. In this case, every SQL request that spends more than 1ms will be printed in the log as

Re: While enabling JCache, JCacheMetrics is throwing NullPointerException in getCacheManager with spring boot

Hi, looks like your question is already answered here http://apache-ignite-users.70518.x6.nabble.com/values-retrieved-from-the-cache-are-wrapped-with-JdkDynamicAopProxy-while-using-springboot-and-JCache-tp23258p23426.html Thanks, S. пн, 13 авг. 2018 г. в 15:14, daya airody : > Hi slava, > > I

Re: distributed-ddl extended-parameters section showing 404 page not found

; id int, > city_id int, > name varchar, > age int, > company varchar, > PRIMARY KEY (id, city_id) > ) WITH "template=partitioned,backups=1,affinitykey=city_id, key_type=PersonKe > > > > which one works？ > -- > *发件人:* Вячесла

Re: distributed-ddl extended-parameters section showing 404 page not found

Hello, Yep, the link is broken, unfortunately. It seems it should be the following https://apacheignite-sql.readme.io/docs/create-table#section-parameters Thanks, S. ср, 15 авг. 2018 г. в 10:17, Huang Meilong : > I found it here: https://apacheignite-sql.readme.io/docs/getting-started >

Re: Ignite with POJO persistency in SQLServer

Hello, Perhaps, I'm missing something but it seems that LONGVARBINARY is not supported by Apache Ignite. The full list of available types can be found here: https://apacheignite-sql.readme.io/docs/data-types Thanks, S. ср, 8 авг. 2018 г. в 18:52, michal23849 : > Hi All, > > I tried mapping the

Re: While enabling JCache, JCacheMetrics is throwing NullPointerException in getCacheManager with spring boot

Hi, You can create a cache via CacheManager instance using Ignite CacheConfiguration or MutableConfiguration: public class ExampleNodeStartup { public static void main(String[] args) throws Exception { CachingProvider provider = Caching.getCachingProvider(); CacheManager

Re: Failed to add node to topology because it has the same hash code for partitioned affinity as one of existing nodes

Hello, > Hi It is having unique consistentId across cluster. > Node1 ConsistentId (Server 1): 127.0.0.1:48500..48520 192.168.0.4:48500..48520 192.168.0.5:48500..48520 > Node2 ConsistentId (Server 1): 127.0.0.1:48500..48520 192.168.0.4:48500..48520 192.168.0.5:48500..48520 > Node 3(server2):

Re: Failed to add node to topology because it has the same hash code for partitioned affinity as one of existing nodes

Hello, It seems that there are nodes that have the same value of consistentId property. Please try to set IgniteConfiguration.setConsistentId to a unique value cluster-wide. Thanks. вт, 7 авг. 2018 г. в 7:27, kvenkatramtreddy : > Hi Team, > > I have configured my all caches replicated mode

Re: Ignite.NET how to cancel tasks

Hello, Have you checked Ignite log files? Do they contain anything suspicious? I just checked TeamCity and it seems that CancellationTest (that I mentioned above) is OK. Thanks, S. вт, 7 авг. 2018 г. в 9:47, Maksym Ieremenko : > Hi Slava, > > > > >> > using (var ignite = Ignition.Start()) > >

Re: While enabling JCache, JCacheMetrics is throwing NullPointerException in getCacheManager with spring boot

Hello, > org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache with the same name is already started): users This exception means that the cache is already created in the cluster. Please consider using Ignite#getOrCreateCache() method instead of Ignite#createCache() [1]

Re: Ignite.NET how to cancel tasks

Hi Max, > using (var ignite = Ignition.Start()) Is it possible that Ignite node was closed before the cancellation request was processed by an instance of SimpleJob? Could you please check that fact? Perhaps you need to modify your code as follows: var task = ignite.GetCompute().ExecuteAsync(new

Re: Remote Session with Ignite & Cassandra persistence

Hello, Hello, First of all, I would recommend switching to TcpDiscoveryVmIpFinder [1] instead of TcpDiscoveryMulticastIpFinder, and disable IPv6 stack via specifying JVM property -Djava.net.preferIPv4Stack=true. [1] https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder

Re: Ignite Cluster with remote server + Cassandra Persistence

Hello, The first problem is related to a bug in the implementation of `PojoField` class. This is a known issue https://issues.apache.org/jira/browse/IGNITE-8788 Unfortunately, that bug is not resolved yet. In any way, the workaround that I provided above should do a trick. The second issue is

Re: Ignite backups on collocated data

Hello, Yes, backup copies will also be collocated. Thanks, S. пт, 27 июл. 2018 г. в 15:11, kotamrajuyashasvi : > Hi > > Suppose I have two ignite caches and these two caches are collocated based > on a field using AffinityKemapped. Now if I configure same number of > backups > for both the

Re: Ignite Cluster with remote server + Cassandra Persistence

Hello, > Just wondering, can I know why we are creating a custom CassandraCacheStoreFactory? It seems that the problem is PojoField#accessor field which is declared as `transient` and so this field is not serialized/deserialized. Therefore, it can lead to NullPointerException. The `PojoField`

Re: Ignite Cluster with remote server + Cassandra Persistence

Hello, It seems I found the root cause of the issue. Could you please try the following workaround? 1. create your own CacheStoreFactory public class CustomCassandraCacheStoreFactory extends CassandraCacheStoreFactory { private final String persistenceSettingsXml; public

Re: Ignite Cluster with remote server + Cassandra Persistence

Hello, It does not seem to me, that the issue is somehow related to the thread you mentioned. I bet the root cause of the problem is a misconfiguration. At least, the exception message tells me that CassandraCacheStore class cannot be initialized for some reason: java.lang.NullPointerException

Re: LRU policy, on heap - off heap size ?

Hello, Yep, it is expected behavior. You are using on-heap eviction policy and so, this policy removes the cache entries from Java heap only. The entries stored in the off-heap region of the memory are not affected. You can find a comprehensive description here:

Re: Running Server Node in UNIX

Hello, please try the following: java -cp /opt/lib/*:/path-to-your-working-directory-where-class-files-are-stored/ com.cache.init.ServerNodeCodeStartup I think that these links will be very helpful for you:

Re: Tracing all SQL Queries

Hi, Yes, it can be specified in your Spring configuration file as follows: ... Thanks, Slava. пн, 16 июл. 2018 г. в 19:39, ApacheUser : > Hi Slava, > Sorry to get into this thread,I have similar problem to control long > running > SQLs. I want timeout SQLs running more than 500ms.

Re: Apache Ignite Bianry Cache store Sql Read Through Feature

Hi, I could not find something related to that in Jira. So, it seems there are no plans to implement this feature. Thanks, S. чт, 12 июл. 2018 г. в 20:50, debashissinha : > Hi Salva, > > Many Thanks for your advise . So it seems there is no real time way to do > that . However I was also

Re: Tracing all SQL Queries

Hello Dave, I am afraid that there is no such possibility out of the box. The simple workaround that I can imagine is using IgniteConfiguration#setLongQueryWarningTimeout() method and set 1ms for example. In that case, every SQL request that spends more than 1ms will be printed in the log as

Re: Need to Use Both Native and Cache store Persistence

Hello, I think the NodeFilter was designed exactly for that case. Please take a look at this method: CacheConfiguration#setNodeFilter() [1] So, it can be used as follows: - for example, you can add a node attribute - "you-custom-attribute" that can be used to determine the fact that a cache

Re: Ignite with Spring Boot Data JPA

Hello, I don't think I clearly understand the issue you faced. Please provide more details about the problem so that the community can help you. Could create a small reproducer project and share it on GitHub? By the way, the log file from the server node will be helpful as well. Thanks, S. вт,

Re: apache ignite atomicLong.incrementAndGet() is causing starvation in striped pool

Hello Vadym, The root cause of the behavior is that you are trying to use `IgniteAtomicLong` instance within `ContinuousQuery` local listener. In general, you should avoid using cache operations in that listener ( `IgniteAtomicLong` uses IgniteCache under the hood), because this callback is

Re: Can we start an ignite node by passing ignite configuations in json file in case on Dot net Core

Hello, You can use Spring XML in order to configure Ignite instance. Spring config file can be provided via Ignition.Start(string) method and IgniteConfiguration.SpringConfigUrl property. Please take a look at this page: https://apacheignite-net.readme.io/docs/configuration#section-spring-xml

Re: Apache Ignite with Caching : How do I sure that cache(s) has all datas?

Hi, CacheWriteSynchronizationMode defines the behavior of cache during modification operations. I mean IgniteCache#put(), #remove() etc. For example, in case of 'PRIMARY_SYNC', a thread that executes modification operation will wait for completion of operation on primary node only, backups will

Re: Not getting the column access in Ignite Cache created and loaded from Oracle

Hello, What method do you use in order to create SQL tables into Ignite? - DDL command - CREATE TABLE https://apacheignite-sql.readme.io/docs/create-table - Java API. If it is your case then I guess queryable fields are not properly specified.

Re: Apache Ignite with Caching : How do I sure that cache(s) has all datas?

Hello, I think rebalancing makes sense for all types of caches. It does not matter what type of cache you use. Long story short, a replicated cache is a partitioned cache with the number of backups equals to the number of nodes minus 1. Let's assume that you ingested all data in the cluster, and

Re: Cache configuration in case of Client mode

t;>> I had used SpringApplicationContextResource annotation. But it did not >>>> inject the application context in it. So I decided to use spring managed >>>> bean and it worked. >>>> >>>> Thanks, >>>> Prasad >>>> >>>&g

Re: Cache configuration in case of Client mode

It seems that you need to use @ SpringApplicationContextResource instead of @Autowired. Could you please check that? Thanks. чт, 5 июл. 2018 г. в 17:01, Prasad Bhalerao : > > > import java.io.Serializable; > import javax.cache.configuration.Factory; > import javax.sql.DataSource; > import

Re: NPE When joining grid

Hi Bryan, DiscoverySpi was slightly reworked in AI 2.5 Please take a look at this enhancement proposal: https://cwiki.apache.org/confluence/display/IGNITE/IEP-15%3A+Discovery+SPI+by+ZooKeeper And it looks like, the issue, that you mentioned, was resolved as part of

Re:

Hello, I think ContinuousQuery will be a good choice for your use-case [1] [1] https://apacheignite.readme.io/docs/continuous-queries Thanks! ср, 27 июн. 2018 г. в 18:51, James Dodson : > Hello. > > I am creating a Spring Boot application that gets objects from Kinesis and > uses

Re: ClassCastException When Using CacheEntryProcessor in StreamVisitor

Hi, I was able to reproduce the issue you mentioned. I will debug that use-case and create a JIRA ticket in order to track this. As a workaround, please try to replace the following line: personCache.withKeepBinary().invoke(id, new CacheEntryProcessor<> ... by IgniteCache

Re: A bug in SQL "CREATE TABLE" and its underlying Ignite cache

of type 'java.lang.Long' for key class 'class > java.lang.Long' and value class 'interface > org.apache.ignite.binary.BinaryObject'. Make sure that one of these classes > contains respective getter method or field. > > > > I want to use BinaryObject here for some flexibility. > >

Re: A bug in SQL "CREATE TABLE" and its underlying Ignite cache

Hello, It seems that the root cause of the issue is wrong values of 'KEY_TYPE' and 'VALUE_TYPE' parameters. In your case, there is no need to specify 'KEY_TYPE' at all, and 'VALUE_TYPE' should Person.class.getName() I think. Please try the following: String createTableSQL = "CREATE TABLE

Re: SQL cannot find data of new class definition

Hello, > I use BinaryObject in the first place because the document says BinaryObject “enables you to add and remove fields from objects of the same type” Yes, you can dynamically add fields to BinaryObject using BinaryObjecyBuilder, but fields that you want to query have to be specified on node

Re: unsubscribe

Hello, Hello, To unsubscribe from the user mailing list send a letter to user-unsubscr...@ignite.apache.org with a word "Unsubscribe" without quotes as a subject. If you have a mailing client, follow an unsubscribe link here: https://ignite.apache.org/community/resources.html#mail-lists

Re: What is the expected ETA for the 2.5.0 release...

Hello Paul, The voting has already been started. Please take a look at this topic: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-5-0-RC1-tc30923.html So, I assume AI 2.5 will be released soon. Best regards, S. 2018-05-28 17:10 GMT+03:00 Paul Anderson

Re: Fwd: Re: Ignite cache query

Hello Shaleen, It looks like that you want that SQL engine would create table columns based on the hashmap which has a dynamic structure (obviously you can add and remove keys from the map simultaneously). So, every time when you add/remove a key from the map for a particular entry, SQL engine

Re: Ignite configuration for starting in client mode

Hello Prasad, I think it is not necessary to setup cache configurations and/or data storage config on the client node until you don't use local caches. The most important things that you have to configure are IgniteConfiguration#clientMode(true) [1] and Discovery SPI [2]. [1]

Re: Cache loading from the web console

Hello, Are you looking for an ability to do it (execute IgniteCache#loadCache()) via web console? I don't think there is such capability at the moment. Thanks, Slava. 2018-04-09 15:19 GMT+03:00 demanfear : > About the loadcache () method, I know it's interesting to know

Re: stop sending messages pls

test message 2018-04-02 10:12 GMT+03:00 andriy.kasat...@kyivstar.net < andriy.kasat...@kyivstar.net>: > My email is andriy.kasat...@kyivstar.net. Can you please unsubscribe this > mail. >

Re: stop sending messages pls

Hello, To unsubscribe from the user mailing list send a letter to user-unsubscr...@ignite.apache.org with a word "Unsubscribe" without quotes as a topic. If you have a mailing client, follow an unsubscribe link here: https://ignite.apache.org/community/resources.html#mail-lists Thanks, S.

Re: Ignite 2.3.4 and Spring Boot 2.0.0.RELEASE

Hello, If I am not mistaken, Apache Ignite is certified with spring-data:1.13.1.RELEASE version. I am not sure there is an activity related to the latest code changes in spring boot library. Anyway, you can start a discussion on dev-list about that, and feel free to contribute to the project!

Re: Cancelling a Continuous Query

Hello Andre, As mentioned in the javadoc [1], you have to call QueryCursor#close() method in order to stop receiving updates. // Create new continuous query. ContinuousQuery qry = new ContinuousQuery<>(); // Execute query and get cursor that iterates through initial

Re: Can we enabled persistence per cache level in the java code instead of setting persistence in xml configuration file for entire cluster?

If your question is about a possibility which allows to enable/disable persistence of a data region on the fly, then the answer is no. That property can be configured via XML file or java api. You can find a comprehensive description here

Re: peerclassloading property to true while we are loading data with persistence property set to true?

Perhaps, this page will be useful as well https://apacheignite.readme.io/docs/cluster-activation Thanks! 2018-03-23 17:37 GMT+03:00 Вячеслав Коптилин <slava.kopti...@gmail.com>: > Hi Teja, > > > Is it mandatory to set peerclassloading property to true while we

Re: peerclassloading property to true while we are loading data with persistence property set to true?

Hi Teja, > Is it mandatory to set peerclassloading property to true while we are loading data with persistence property set to true? Peer class loading property is not mandatory. This feature relates to Compute Grid https://apacheignite.readme.io/docs/compute-grid Please check this page for the

Re: Ignite on Kubernetes: Question on external jars

Hello, It seems to me, that you have to restart your cluster. Java classpath is not something that can be dynamically changed at runtime. Thanks! 2018-02-23 12:14 GMT+03:00 vbm : > Hi, > > I have a java program which is used to write to ignite cache and then into > the

Re: how to dismiss a ignite server node.

Hello, If you don't have configured 3rd party cache store or backups, then there is only one possible way, I think. You need to - store all the data from the node you want to shut down, - shut down the node - upload stored data back to the cluster. It can be done via an external database, for

  1   2   >