Ignite TcpDiscoveryS3IpFinder and AWS VPC

I have a cluster running on AWS VPC with TcpDiscoveryS3IpFinder SPI. I noticed that there are a couple of entries in the S3 bucket '127.0.0.1#47500', '0:0:0:0:0:0:0:1%lo#47500' along with entries for the private IPs of the nodes. If anyone understands what these are, can you please share the info.

Re: Ignite data can't be recovered after node fail

Where you able to resolve this? I'm in a very similar situation. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Uneven partitioning and data not on off-heap memory.

Thanks Denis. That makes sense. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Uneven partitioning and data not on off-heap memory.

> 2. By default all entries are saved off heap (not disk, heap outside the Java heap to avoid GC problems), you can configure it to use heap or off heap memory as you want. This is the output from visor. I'm not completely sure what the difference between off-heap and off-heap memory is here. S

Uneven partitioning and data not on off-heap memory.

I have started my cluster and pushed some data into a cache. Cluster details are provided below. The cache has persistence enabled. I see a couple of issues with how data is cached. 1. Out of 8 nodes only 2 nodes have some entries. I ran all my keys through Murmur3 hash and they seemed to be evenly

Re: Deadlock during cache loading

I have a fairly similar setup. What type of EC2 instances are you using? Just for compare my setup. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: OutOfMemoryError while streaming

Thanks again. I have one more question. After pushing some data, I see only two nodes having entries out of 8. All the others have 0 entries. My keys are 9 char long strings with a common prefix (all have the same first 3 chars). Wondering why the keys are not evenly distributed. -- Sent fro

Re: OutOfMemoryError while streaming

breischl, Thanks for the quick response. I'm not sure why the node stats show Non-heap memory maximum | 744mb Each server node has 32GB and I've assigned 3g for heap. Shouldn't this be 16GB since that's what I set the data region size to? -

OutOfMemoryError while streaming

I'm seeing OutOfMemoryError when I have multiple data streamers pushing data into the cluster. My cluster consists of 8 servers running one node each. Each server has 32GB RAM and 4 Cores. All the nodes are started like this = bin/ignite.sh -J-Xmx3g config/dev-cluster-config.xml ===

Service grid vs AWS Auto Scaling

I have ignite data grid and I'm looking to build a REST service on top to serve this data. Looks like I have two choices here.  1. I can build a plain web service which will act as a client node on the ignite cluster and place that in AWS auto scaling group (For scaling up during peak hours and als