Ignite hanging (dead looping) at TCP discovery stage

Hi, We are running an ignite cluster by TcpDiscoverySharedFsIpFinder. It works well until we installed docker on the machine. After docker is installed, docker created a NAT Ethernet adapter vEthernet (DockerNAT): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . :

Re: can't get or query but scan works

sorry, nvm, it was a wrong setup. both work now. sorry for the spawn On Thu, Aug 8, 2019 at 4:12 PM relax ken wrote: > to correct the query, I did set args > > `userDBRecordCache.query(new SqlFieldsQuery("select userId from " + > UserIgniteRecord.class.getSimpleNam

Re: can't get or query but scan works

to correct the query, I did set args `userDBRecordCache.query(new SqlFieldsQuery("select userId from " + UserIgniteRecord.class.getSimpleName() + " where username = ?").setArgs(userName));` copied a wrong one in my last email On Thu, Aug 8, 2019 at 4:09 PM relax ken wr

can't get or query but scan works

Hi, I am trying to use ignite query and indexing by following ignite example but can't get it work. Here is my entity class: public class UserIgniteRecord { @QuerySqlField(index = true) public final String userId; @QuerySqlField(index = true) public final String username;

Re: Node joining didn't trigger Affinity recalculation problem

is > > > On Fri, Apr 19, 2019 at 10:32 PM relax ken wrote: > >> Great! Thanks Denis! that's the issue. After I configured it in security >> group, it works >> >> On Sat, Apr 20, 2019 at 6:03 AM Denis Magda wrote: >> >>> By default, each node wil

Re: Node joining didn't trigger Affinity recalculation problem

DiscoverySpi.java#L771 > [2] > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.java#L782 > > - > Denis > > > On Fri, Apr 19, 2019 at 9:38 PM relax ken wrote: > >> I don't think both nodes joined

Re: Node joining didn't trigger Affinity recalculation problem

your cluster > topology. Might be some networking issue. > > - > Denis > > > On Tue, Apr 16, 2019 at 9:53 AM relax ken wrote: > >> Hi, >> >> I wrote an aws ELB based tcp discovery ip finder. When I launched two ec2 >> nodes in the same target group,

Node joining didn't trigger Affinity recalculation problem

Hi, I wrote an aws ELB based tcp discovery ip finder. When I launched two ec2 nodes in the same target group, the ip finder found node IPs correctly. However, affinity recalculation wasn't triggered. Basically nothing happened. also no exception. If I ran two nodes locally with multicast,

Re: InvalidClassException local class incompatible for custom cache store factory

he and start it with a new config. > Different implementations of cache store on different nodes is not a > correct situation, so you should avoid it. > > Denis > > вт, 19 мар. 2019 г. в 20:30, relax ken : > >> Hi, >> >> I am testing my custom CacheStoreFactor

InvalidClassException local class incompatible for custom cache store factory

Hi, I am testing my custom CacheStoreFactory. It worked fine previously on my local dev machine. After I changed this class and run it, I got `java.io.InvalidClassException: xxx.CacheStoreFactory; local class incompatible: stream classdesc serialVersionUID = 7199421607011991053, local class

Re: Why does write behind require to enable write through?

ttps://static.javadoc.io/javax.cache/cache-api/1.1.0/javax/cache/configuration/MutableConfiguration.html#setWriteThrough-boolean- > > вт, 5 мар. 2019 г. в 16:59, relax ken : > > > > Thanks Ilya. I guess conceptually there are many explanations and > definitions about those

Re: Why does write behind require to enable write through?

options to avoid any unexpected behaviour. On Tue, Mar 5, 2019 at 1:46 PM Ilya Kasnacheev wrote: > Hello! > > It is because write-behing is a kind of write-through. Like random access > memory is a kind of computer memory. > > Regards, > -- > Ilya Kasnacheev > > > вт,

Why does write behind require to enable write through?

Hi, I am new to Ignite. When I enable write behind, I always get a warning "Write-behind mode for the cache store also requires CacheConfiguration.setWriteThrough(true) property." Why does write behind require write through when I am using write behind only? Here is my configuration