ignite

问题 Single ignite node running with my application and it doesn't start because ignite constantly tries to find some other node Log is filled with messages like: o.a.i.s.d.tcp.TcpDiscoverySpi - TCP discovery accepted incoming connection [rmtAddr=/127.0.0.1, rmtPort=59459] o.a.i.s.d.tcp.TcpDiscoverySpi - TCP discovery spawning a new thread for connection [rmtAddr=/127.0.0.1, rmtPort=59459] o.a.i.s.d.tcp.TcpDiscoverySpi - Started serving remote node connection [rmtAddr=/127.0.0.1:59459, rmtPort

问题 Ignite 2.8.0, I enable persistent, code like this: IgniteConfiguration igniteCfg = new IgniteConfiguration(); //igniteCfg.setClientMode(true); DataStorageConfiguration dataStorageCfg = new DataStorageConfiguration(); dataStorageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true); igniteCfg.setDataStorageConfiguration(dataStorageCfg); Ignite ignite = Ignition.start(igniteCfg); Then some exception like below: Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining

问题 I am starting ignite by a specific configuration. In that configuration, I specified expiration policy. But expiration is not working. When I specified a cache name in that property, it is working fine. I added configuration like below <property name="expiryPolicyFactory"> <bean class="javax.cache.expiry.CreatedExpiryPolicy" factory-method="factoryOf"> <constructor-arg> <bean class="javax.cache.expiry.Duration"> <constructor-arg value="MINUTES"/> <constructor-arg value="5"/> </bean> <

问题 We are implementing Apache Ignite's transaction using org.apache.ignite.transactions. Transaction object. But we would like to know if it supports SQL Querying. 回答1: No, you can't properly use SQL transactions, though Ignite has an experimental support for MVCC. I'd suggest you to keep using the Transaction object and K-V API. Please, follow the links: https://apacheignite.readme.io/docs/transactions#section-atomicity-mode and https://apacheignite-sql.readme.io/docs/multiversion-concurrency

问题 This is the ignite(version 2.7.5) configuration that I am using for my 2-node PARTITIONED cluster. <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <!-- Enable annotation-driven caching. --> <bean name="noOpFailureHandler" class="org.apache.ignite.failure.NoOpFailureHandler"/> <bean id="ignite.cfg" class=

问题 This is the ignite(version 2.7.5) configuration that I am using for my 2-node PARTITIONED cluster. <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <!-- Enable annotation-driven caching. --> <bean name="noOpFailureHandler" class="org.apache.ignite.failure.NoOpFailureHandler"/> <bean id="ignite.cfg" class=

问题 This is the ignite(version 2.7.5) configuration that I am using for my 2-node PARTITIONED cluster. <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <!-- Enable annotation-driven caching. --> <bean name="noOpFailureHandler" class="org.apache.ignite.failure.NoOpFailureHandler"/> <bean id="ignite.cfg" class=

来源： https://stackoverflow.com/questions/64728898/for-ignite-how-can-i-use-the-same-classes-in-different-packages-without-overrid

来源： https://stackoverflow.com/questions/64728898/for-ignite-how-can-i-use-the-same-classes-in-different-packages-without-overrid

来源： https://stackoverflow.com/questions/58444937/failed-to-join-apache-ignite-topology-when-multiple-server-pods-starts-at-the-sa