subscribe

Please subscribe me -- Thanks & Regards, Naveen Bandaru

Implementing HA among Ignite Clusters

Hi All We have 2 clusters (Primary and secondary) running and both are always in sync from data perspective. Always consumers are using Primary only, but when primary is not reachable, it should get redirected to secondary cluster How can this be achieved ? 1. Can we do anything on the cluster

RE: Could not clear historyMap due to WAL reservation on cp

Hi, Could you share the full logs with the exception? There is an interesting  JIRA ticket that could be the reason for this [1] [1] - https://issues.apache.org/jira/browse/IGNITE-13373   From: shivakumarSent: Thursday, December 3, 2020 10:51 AMTo: user@ignite.apache.orgSubject: Could not clear his

RE: WAL is growing exponentially

Hi, What version do you use? Is it possible to share the full log files?  From: rihan123Sent: Friday, December 4, 2020 2:32 PMTo: user@ignite.apache.orgSubject: WAL is growing exponentially HiI am doing POC to see if Ignite is good for my usecase and i achievedrequired data ingestion rate but after

RE: Implementing HA among Ignite Clusters

Hi, I don’t think that ignite support this out of the box, cause data replication is something beyond the default distribution. The usage depends on how your data is replicated, whether you want active-active synchronization, and so on.  But if it’s about switching from one cluster to another, and

Apache Ignite C#/.NET: Asynchronous Execution example failing - facing different errors

Hello, I tried to follow the Asynchronous Execution example in the Apache Ignite docs, however I ran into some errors, and the errors vary to the different implementations I have. *Variat

Re: Implementing HA among Ignite Clusters

This DR feature is what you are looking for, complete solution: https://www.gridgain.com/docs/latest/administrators-guide/data-center-replication/introduction On Sunday, December 6, 2020, Alexandr Shapkin wrote: > Hi, > > > > I don’t think that ignite support this out of the box, cause data > re

With as syntax does not work in ignite 2.9.0?

Hello. We use 'with xxx as (select xxx) ',which works vrey fine in 2.8.1 and other past release versions.After we uprade to 2.9.0,such sqls start to throw exception. In the server side,the error looks like: , args=Object[] [], stmtType=SELECT_STATEMENT_TYPE, autoCommit=true, partResReq=false, su

RE: Implementing HA among Ignite Clusters

HI We have no issue with the data replication, we do have feeder services feeding data into multiple clusters real time. And, we are going to have active active set up only, but secondary is only used in case primary has any issues. At the moment, consumers use the full connection string like CL