ignite

问题 I see that with a change introduced in 2.4 in IgniteSpringBean to delay ignite instance start until all other spring beans are initialized may have broken Ignite SpringTransactionManager resulting in inability to configure it for Spring transaction abstraction of Ignite transactions. I really, badly need to find a way to work around this. Any ideas/suggestions anyone? Below is the line from IgniteSpringBean java doc "Ignite instance is started after all other Spring beans have been

问题 Reading the documentation in https://apacheignite.readme.io/docs/affinity-collocation and in ignite-examples, the example for using @AffinityKeyMapped assumes that the key is an object: PersonKey is a class with personId and companyId, and companyId has the annotation. In my use case my key is a simple integer. I am using the domain model generated from WebConsole. I have 2 classes: Item and ItemInstance, and ItemInstance has a foreign key reference to Item. My model is defined as follows:

问题 How I sure such a this condition always true: Let's say I have 3 tables which are contains 1000, 2000, 3000 records. And I have to load that all records to the cache, but I want to be sure all the data is in cache before Client using this cache. Note that cache mode is replicated. Apache Ignite has this future? Here is the things that I will plan to do: I will set the "atomicityMode" to the "TRANSACTIONAL" I will create class for cacheStoreFactory This class contains loadCache method extends

问题 Ignite logs have starvation waringings and stop to provide service: [12:55:22,080][WARNING][grid-timeout-worker-#71][G] >>> Possible starvation in striped pool. Thread name: sys-stripe-25-#26 Deadlock: false Completed: 16272032 Thread [name="sys-stripe-25-#26", id=51, state=WAITING, blockCnt=79, waitCnt=15616666] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304) at o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)

问题 I am trying to integrate ignite with cassandra. I set up the configuration and started the ignite node. But I can not insert/read data from Ignite cache/cassandra db. I created Keyspace and table in the cassandra. And inserted some values. But when tried to read the values , the exception arises. Same thing happened when I tried to insert some values. My Ignite version is 2.6 and cqlsh 5.0.1 | Cassandra 3.11.4 | CQL spec 3.4.4 | spark version is 2.3.0 | scala version is 2.11.8 | cassandra

问题 I understand from the docs that replicated caches are implemented using partitioned caches where every key has a primary copy and is also backed up on all other nodes in the cluster & that when data is queried lookups would be made from both primary & backup on the node for serving the query. But i see that the default cache write synchronization mode is PRIMARY_SYNC, where client will not wait for backups to be updated. Does that mean i have to explicitly set it to FULL_SYNC for replicated

问题 I'm using Ignite.NET 2.7.6. There is a configuration from one server and about 40 clients. After 8 hours of work, the server starts behaving strangely: clients cannot connect it, some queries have no result, etc. On the server's side, the memory consumption is ok, the amount of threads is about 250 and all looks ok. I don't see any problems, so I decided to solve all the problems on the server's side that were marked as SEVERE. The first one I encounter is: Blocked system-critical thread has

问题 I want to run multiple Ignite nodes on the same VM. Suppose, their address will be localhost:port (a set of ports, as a series). And, I want my Java client application to connect to the nodes. Can you provide a simple and beginner-level guide to achieve this? The ones I tried are overwhelming. 回答1: public class MultipleIgnites { public static void main(String[] args) throws Exception { Ignition.start(new IgniteConfiguration().setIgniteInstanceName("s1") .setDataStorageConfiguration(new

问题 How can I provide an authentication for my Apache ignite cluster. Basically I'm looking for setting username and password. Otherwise allowing list of trusted(white listed) clients is also fine. 回答1: This can be implemented by your own: https://apacheignite.readme.io/docs/advanced-security or you can use 3rd party-ready solutions: https://docs.gridgain.com/docs/security-and-audit 回答2: Apache Ignite does not provide these kinds of security capabilities with its open-source version. As mentioned

问题 I'm getting the error "Conflicting type IDs [type1='Row', type2='Row', typeId=113114]" after upgrading from Apache Ignite 2.0 to 2.1 (.Net). I didn't change any code after upgrading, so am wondering if the expectation on how to create and use dynamic Binary Objects changed? I looked at the AddType method. Maybe it should be returning instead of throwing, and maybe the name of the method is misleading and it should be GetOrAddType? AddType Method: https://github.com/apache/ignite/blob