Re: Cache.put latencies high

I did simple sequential puts to the cache. The latencies kept spiking intermittently to 30ms or higher. The test took about 30 minutes to load 1M records. I am using the s3 ip finder for discovery. I would expect 1-2 ms at max putting to a cache per request, but 30 ms seems a little higher.

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 wrote: > Hi, > > I have been trying to setup Zeppelin 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