Web session httpSession issue.

Hi, I have used Web session clustering. The web session is clustered across the nodes, I am happy about that. But there is one issue I found. In my application I store *UserInfo* object inside the httpSession object inside one of my spring controllers. When my view gets loaded( which is a *JSP

Re: Affinity key & data rebalancing

As expected. Thank you Ilya for response. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite swap space

I have, -4 nodes 2 clients & 2 severs. A & B are the clients and X & Y are the servers. -32 GB RAM -2 data regions default & xyz -A & B takes 2 GB RAM each. X takes 10 GB & Y takes 15 GB but may grow to 25 GB -X uses default region and Y uses xyz region All the above nodes run

Doubt regarding CACHE Replication.

I am using Ignite with persistence mode enabled. I created a cache and let it grow in one server node till the data is upto 2 GB. After some time, if I start a new server node and since the cache is in replicated mode, why the data is not replicated in the new server node? Any idea? It's showing 0

Re: Query execution is too long issue!

Hi, Most likely you need to optimize the query or do revisit your Ignite memory and cluster configuration. My suggestion would be to start by checking these performance notes. Let us know if you have any specific questions:

RE: Apache Ignite 2.8 ETA

Very cool. SCott Scott Cote Senior Application Developer - Java | Electronic Transaction Consultants Corporation (ETC) 1600 N. Collins Boulevard, Suite 4000, Richardson, TX 75080 (o) 469.248.4576 | (c) 972.900.1561 [cid:image005.png@01D5D6B2.A4015090]

Re: cache put/clear atomicity query

The errors are still caused by the breakpoint and not the code you’re trying to test. I think “replace" returns false if there’s no existing value (or the value is not the one you specify, depending on which method you use), true if it succeeded. > On 29 Jan 2020, at 12:20, Narsi Reddy

Re: How to choose Leader manually?

Hi there, Firstly let me clarify that I am just an Ignite user - not an Ignite team member/expert...so it will be great to get the views of the experts in this discussion... Now, in Ignite, all data gets 'stored' in a 'CACHE'. If you want your data to be persisted, you simply configure your

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

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

Re: How to choose Leader manually?

Hi, As I understand it - if you are connecting via the JDBC Thin Client, in the connection-string, you would list only the endpoints of the servers in the 'Main Purpose' datacenter. To failover to servers in the other datacenter however, you would have to change your connection string and

Re: cache put/clear atomicity query

Now, I tried pausing replace method at before said point for just 1sec and It throws below error. So in production if this sequence occurs, node1->is executing replace and in between node2->executed remove, what be the outcome would replace method return 'false' because it did not succeed or

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

Re: cache put/clear atomicity query

That is an error you get if the JVM pauses for too long. Most often this is a sign of poorly configured garbage collection but in this case is almost certainly because you stopped the node in the debugger. This is not caused by the use of replace or clear. > On 29 Jan 2020, at 07:22, Narsi

Re: K8S Deployment with Cache Partitioning

When you say “replicas” are you talking about the number of pods, i.e., the “kubectl scale sts ignite --replicas=4” command? If so, that’s not related to your cache configuration. That’s simply the number of nodes in your cluster. If you loaded in the SQL file as described at the end of the

@SpringResource not injected

I am trying to create a class: public class SecurityPriceDTOStore extends CacheStoreAdapter{ with some resources taken from the Spring context. I tried multiple things like: @SpringResource(resourceName ="service") public transient String service; @Autowired @Qualifier("dataSource")

K8S Deployment with Cache Partitioning

Hi, I'm trying to deploy Ignite with K8S with cache partitioning enabled. I went through [1] and found out ignite-deployment.yaml include all configurations to create replicas of the dataset. However, in my case, I'm interested in the partitioning of the cache not just replicating. Appreciate

JVM Crashing with SegFault on org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write0

Hi All, We are seeing JVM on an ignite node, the error trace taking us to org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write0 Below is full stacktrace of error. We are running ignite 2.7.0 with openjdk 1.8 on RHEL machines. Can someone please check and suggest

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