Re: Node discovery

Sorry, my mistake. I realized it was a networking issue. Its fixed now. What ports should I be whitelisting for the setup to work in a firewall? On Mon, Mar 21, 2016 at 11:33 AM, babu prasad <babu...@gmail.com> wrote: > Thank you! > Here is the configuration. >

Node discovery

Hi, I am trying to automate ignite cluster build. I am using apache-ignite-fabric-1.5.0.final-bin.zip. Looks like the nodes are starting up as individual nodes and not as part of the cluster. I tried using both the AWS configuration(using S3) and static IP and I am still running into the issue

Re: Cache.put latencies high

And finally you should verify that network works well in your environment. > Do you have 10G ethernet? > > D. > >> On Tue, Jan 12, 2016 at 8:27 PM, babu prasad <babu...@gmail.com> wrote: >> Hi, >> >> I have configured 2 ignite servers with a heap siz

Apache Ignite client on AWS Lambda

Hi, I almost got Ignite client running on AWS Lambda. But then, I hit this error, Caused by: class org.apache.ignite.IgniteCheckedException: Failed to bind time server socket within specified port range [locHost=ip-10-0-73-203.ec2.internal/10.0.73.203, startPort=31100, endPort=31199] at

Re: Help with Ignite-Zeppelin

I was using Amazon EMR. Looks like there 1.4 jars. Copied over the 1.5 jars, created a new ignite-jdbc.xml and updated the jdbc url to use the new jdbc url. Did the trick! On Sun, Jan 17, 2016 at 3:50 PM, babu prasad <babu...@gmail.com> wrote: > Hi, > > I have been trying to

Help with Ignite-Zeppelin

Hi, I have been trying to setup Zeppelin to talk to Apache Ignite, but no success. I have my ignite servers running on remote nodes. I keep getting this error. I followed this documentation to set it up - http://apacheignite.gridgain.org/v1.1/docs/data-analysis-with-apache-zeppelin ERROR

Re: Loadcache behavior

Thanks! This may still not help because my underlying datastore is a warehouse where only batch queries are efficient, Also, it looks like the key to partition mapping could change if the no of partitions in the aff function , which will result in unnecessary backfills. I think I might need to

Compression on Ignite

Does ignite compress data in memory or is the data stored as such? If there is no default compression, do you intend to provide an option at a later point? While storing large amounts of data in a distributed cache, compression may help a lot.

Loadcache behavior

I was loading data from AWS Redshift into Ignite through the loadcache API. cache.loadCache(null, "java.lang.Integer", "select * from lineorder where lo_orderdate > 19970101"); I ran this from a single client. The query basically ran on all the nodes. I had 1 client and 2 servers and the same

Cache.put latencies high

Hi, I have configured 2 ignite servers with a heap size of 8G each. Running with backups=1 and primary_sync mode. Ignite servers are being used as a write behind cache for my Aurora database. I am trying to run a load test with 3 clients talking to the remote cache in the 2 ignite servers. All