Questions regarding Data Availability/Replication. @Ignite Team, please answer as it's important for us.

Scenario: Datacenter 1 (Main) -> One Application Server (Client Node CN1) and One DB Server (Server Node SN1). Datacenter 2 (Recovery) -> One Application Server (Client Node CN2) and One DB Server (Server Node SN2). Usually all the user requests go to CN1 but not CN2. So, technically we will not

Re: How to choose Leader manually?

Thanks jose for the prompt reply. Based on what you reply, I can understand that using DriverManager I can query a particular node. But my question is regarding replication and data availability. So, please let me rephrase my question. Scenario: Datacenter 1 (Main) -> One Application Server (Cli

How to choose Leader manually?

Hi. Here is the use case: If I deploy ignite in a cluster where logically, it sees four data nodes, but physically, I am going to use two nodes as "Main Purpose" nodes and two nodes as "Disaster Recovery" nodes. Let's say two Data Centres holding two nodes each. If I enable replication across al

Query execution is too long issue!

When querying via some java application and if the topology is in such a way that two clients connect to one server node, then some times we are getting an exception saying query execution is too long. This is the SQL schema for table stmt.executeUpdate("CREATE TABLE DOCIDS (" + " id LONG P