Amazon AWS EC2 settings

We are running ignite on AWS EC2 instance. We are not using S3 based discovery but using zookeeper based discovery and it seems to work fine. While reading some of ignite documentation I came across this that suggests using "significantly greater than the default" value for socket timeout for EC2

Re: Ignite cluster

vkulichenko wrote > Ignite doesn't have full segmentation resolution support out of the box. > With Ignite you will always end up with two independent working cluster in > case of segmentation. You will then have to restart on of these clusters, > but if there were updates on the restarted cluster

Re: Not able to join cluster with Zookeeper based IP finder

Thanks Nikolai. I'll try this. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Not-able-to-join-cluster-with-Zookeeper-based-IP-finder-tp9311p9574.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Not able to join cluster with Zookeeper based IP finder

Nikolai Tikhonov-2 wrote > Hi! > > It's right way to use AddressResolver for deployment in docker. Could you > please share your address resolver implementation? Here's code we are using to configure AddressResolver. Like I mentioned earlier, it's not that this code is not working. It works fine

Re: Not able to join cluster with Zookeeper based IP finder

Yakov - I'll try to see if I can remove AddressResolver. The main reason for adding it was because we are running it inside docker container and if we run docker in BRIDGE mode then the IP address of host is not available to ignite running inside docker container. -- View this message in context

Re: Not able to join cluster with Zookeeper based IP finder

Yakov, We are configuring 47101 port for external address resolver. I provided code we use to configure ignite node in my original post. Essentially for one of the node it will be like this: (port 47101 is just one port we chose as it was one of unused port) Are you suggesting if we use address

Re: Not able to join cluster with Zookeeper based IP finder

I removed 3rd client node from cluster as it's not relevant for this issue. Here's logs for both nodes with quiet mode set to false: node1.log node2.log

Re: Not able to join cluster with Zookeeper based IP finder

Yes, issue is only reproducible when nodes are started simultaneously. We are using marathon (on mesos) to start apps so we don't have control over when node starts. Marathon almost always starts multiple instance at same time. I'm attaching logs for both nodes as well entrie from zookeeper. Pleas

Not able to join cluster with Zookeeper based IP finder

We are seeing intermittent issue where ignite node is not able to join the cluster for our specific configuration. Our ignite instances are part of spring boot application and it’s running inside docker container. These docker container gets deployed by marathon framework on mesos. When we try to s

Re: CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

I converted my config to XML and still getting same error ("Failed to get Cassandra DataSource cause Spring application context wasn't injected into CassandraCacheStoreFactory"). I looked at SpringApplicationContextResource documentation and it's supposed to be used within instance of following cl

Re: CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

It looks like I'll have to convert all Ignite and cache configuration to XML. Just putting cassandra config in XML doesn't seem to work. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CassandraCacheStoreFactory-injection-error-while-trying-to-use-Cassandra-as-

Re: CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

Is this issue related to this defect: https://issues.apache.org/jira/browse/IGNITE-3314 -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CassandraCacheStoreFactory-injection-error-while-trying-to-use-Cassandra-as-persistent-store-tp5689p6183.html Sent from the A

Re: CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

Hi, This was working fine in single node cluster but got into same error once I started second node in cluster. Debugging it further, it looks like when we initialize Ignite object (using Ignite ignite = Ignition.start(ic);) it detects all cache store settings from other node and tries to initial

Re: CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

Thanks Denis. I was initializing data source using setDataSource() but the problem was with the bean I was using to initialize setDataSource() with. Issue is resolved about fixing that bean. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CassandraCacheStoreFacto

CassandraCacheStoreFactory injection error while trying to use Cassandra as persistent store

Hi, I'm trying to use Cassandra as persistent store for my cache. I'm following example given online but trying to configure CassandraCacheStoreFactory using java instead of xml. I know there's limitation because of serialization but just wanted to try it out first. I keep getting exception "Faile