Unable to access Ignite Ec2 Instance from Local PC

2019-08-08 Thread sri hari kali charan Tummala
Hi All, I am trying to connect a ignite ec2 instance (one node) remotely from local PC Mac Intellij Idea I am using TcpDicoverySpi to connect ignite ec2 instance public IP but its failing to connect I did open all the ports I was able to do ssh and ping the host from my local PC even on the remote

Re: Affinity collocation and node rebalancing

2019-08-08 Thread Denis Magda
Thanks for raising the questions! We'll update the documentation accordingly clarifying some tricky areas and scenarios. - Denis On Thu, Aug 1, 2019 at 1:33 PM lhendra wrote: > Denis, again this is really great - definitely something that I will take > into consideration during the schema desi

Re: Ignite 2.7.0: Ignite client:: memory leak

2019-08-08 Thread Denis Magda
As an update, this issue has been included into Ignite 2.7.6 release scheduled for this month. - Denis On Tue, Aug 6, 2019 at 12:37 PM Ilya Kasnacheev wrote: > Hello! > > We did not change it since it should never be a problem anymore. The > rationale is that I can't prove that some history si

RE: Running Ignite Cluster using Docker containers

2019-08-08 Thread vitalys
localhost:47500..47504

RE: Running Ignite Cluster using Docker containers

2019-08-08 Thread Alexandr Shapkin
Most likely you need to get them aware of each other. I.e. configure DiscoverySpi addresses range to 49500..49509. Please, share you Ignite config for containerized nodes. Alexandr From: vitalys Sent: Thursday, August 8, 2019 9:00 PM To: user@ignite.apache.org Subject: RE: Running Ignite Cluster

RE: Running Ignite Cluster using Docker containers

2019-08-08 Thread vitalys
Here is the problem. I can start one Server Node in the Docker container and I can connect to that Node from my client application. However When I run another Docker Containers they are not joining the Cluster. Here is an example : Node 1 : docker run --rm --name myignite1 -p 47501:47500 -p 471

Ignite Spark Example Question

2019-08-08 Thread sri hari kali charan Tummala
Hi All, I am new to Apache Ignite community I am testing out ignite for knowledge sake in the below example the code reads a json file and writes to ingite in-memory table is it overwriting can I do append mode I did try spark append mode .mode(org.apache.spark.sql.SaveMode.Append) without stoppin

Re: can't get or query but scan works

2019-08-08 Thread relax ken
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.getSimpleName() + " where username = > ?").

Re: can't get or query but scan works

2019-08-08 Thread relax ken
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 wrote: > Hi, > > I am tryin

can't get or query but scan works

2019-08-08 Thread relax ken
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: AtomicReference issue with different userVersions

2019-08-08 Thread Ilya Kasnacheev
Hello! Can you throw together a small reproducer project for this behavior? Regards, -- Ilya Kasnacheev чт, 8 авг. 2019 г. в 16:44, Niels Ejrnæs : > Hey all, > > > > Am I wrong in assuming I can do this directly when running a client with a > different userVersion? > > IgniteAtomicLong atom

AtomicReference issue with different userVersions

2019-08-08 Thread Niels Ejrnæs
Hey all, Am I wrong in assuming I can do this directly when running a client with a different userVersion? IgniteAtomicLong atomicLong = ignite.atomicLong("long", 0, false); I get this Exception when running DeploymentMode CONTINUOUS and trying to access either AtomicReferences or AtomicLongs

RE: Running Ignite Cluster using Docker containers

2019-08-08 Thread Alexandr Shapkin
Hello, Please, refer to the docker port forwarding documentation [1] In other words, instead of -p 47503:47503 you need to write -p 47503:47500, unless you have not configured the default discovery spi port to 47503 explicitly. Please, recall that Ignite requires a minimum set of open ports f