Issue with large number of Continuous Queries

*Topology*: Server-1 --> Cache myCache, holds continuously updating data like market data(prices, status, tradetime etc) for instruments. InstrumentId is the key for this cache. Server-1 running with following jvm params: -Xms1g,-Xmx6g Client-1 --> Pushing continuous updates on

Ignite on yarn doesn't started

Hi, All! I tried to run Ignite on Yarn My cluster properties: #IGNITE_HOME = /tmp/ignite # The HDFS path to the Apache Ignite config file. IGNITE_XML_CONFIG = /tmp/ignite/config/default-config.xml # The directory which will be used for saving Apache Ignite distribution. #IGNITE_WORKING_DIR =

REST API on top of ignite using node express

Hi , We are trying to build an Rest API on top of ignite cache using node express. Following is the way we are fetching data from ignite. await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT)); const cache = igniteClient.getCache(CacheNAME); const querysql=new SqlFieldsQuery("SqL")

baseline topology questions

Hi All, Sorry if these questions are too basic. 1) How does cache replication work in context of native persistence, especially in context of WAL files? Do the primary and replication node have separate WAL files? 2) How does baseline topology work in context of kubernetes, with persistent storage

Re: Issue with BaselineTopology Branching History

I also have seen a similar error: Caused by: org.apache.ignite.spi.IgniteSpiException: BaselineTopology of joining node (b1a557be-4a89-42d8-9837-ece339088cc4) is not compatible with BaselineTopology in the cluster. Joining node BlT id (4) is greater than cluster BlT id (0). New BaselineTopolog

Re: Offheap memory consumption + enabled persistence

Hi, Growth of this metric will be stopped after all partitions(1024 by default) allocate memory for maximum count of entries that can be stored in it simultaneously. It will take some time for 1024 partitions(not 100 iterations). You can check it by setting partitions count to smaller size:

Re: Serialisation issue.

Hi, I'm able to start the cache with this configuration. Which version do you use? Can you share small project with a reproducer, as this code snippet works without a problem? Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Need help for Access Violation

Yes. I was using MSVC for both of them. BTW, are the project odbc and thin-client in the ignite needed? I did not build them because of some compiling issues. On Mon, Feb 10, 2020 at 5:54 AM Igor Sapego wrote: > The issue looks very weird to me. Have you compiled the Ignite > libs using the sam

REST API on top of ignite using node express

Hi , We are trying to build an Rest API on top of ignite cache using node express. Following is the way we are fetching data from ignite. await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT)); const cache = igniteClient.getCache(CacheNAME); const querysql=new SqlFieldsQuery("SqL")

Ignite on yarn doesn't started

Hi, All! I tried to run Ignite on Yarn My cluster properties: I also tried to add hdfs:// before paths, but result is the same. I created dir /tmp/ignite on local node fs and copied it to hdfs. then run yarn jar ignite-yarn-2.7.6.jar /tmp/ignite/ignite-yarn-2.7.6.jar /tmp/ignite/cluster.propert

REST API on top of ignite using node express

Hi , We are trying to build an Rest API on top of ignite cache using node express. Following is the way we are fetching data from ignite. await igniteClient.connect(new IgniteClientConfiguration(ENDPOINT)); const cache = igniteClient.getCache(CacheNAME); const querysql=new SqlFieldsQuery("SqL")

Re: Need help for Access Violation

The issue looks very weird to me. Have you compiled the Ignite libs using the same compiler as you use in your project? Best Regards, Igor On Fri, Feb 7, 2020 at 7:39 PM Anthony wrote: > Hello, > The "usrCp" value is > NameValueType > ▶ usrCp const std::string & > Seems that the "cfg.jvmClass