RE: Error:data-streamer-stripe....Timed out while waiting for schema update.

Hi, I am using these options to increase size -J-Xms6000m -J-Xmx6m while i am trying to increase heap size and on start again it's showing required size more everytime. first time running exe: # IgnitePersistenceApp.exe -J-Xms5000m -J-Xmx5m -J-XX:+UseParNewGC -J-XX:+AlwaysPreTouch

Performance turning - large transaction

Hey all Looking for an independent consultant that can help us with some ignite performance turning and a general architecture/configuration health check. Part-time couple hours here and there, or in a block of time. Please contact me directly. Thanks Ryan

RE: Error:data-streamer-stripe....Timed out while waiting for schema update.

Hi Siva, Nodes started on local machine require more than 80% of physical RAM whatcan lead to significant slowdown due to swapping (please decrease JVM heapsize, data region size or checkpoint buffer size) [required=78152MB,available=65535MB] According to the warning, you don’t have enough heap

Re: 2.8.1 : INFO org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted incoming communication connection

Hi Ilya, Please find the video recording of the issue I face. https://drive.google.com/file/d/1fDqxmgjiL3o_eenHoUosdiYlMMBJ4xVj/view?usp=sharing regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Multithread transactions in a C++ Thin Client

Ok... thanks Igor! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Ignite rebalancing when a server is rebooted w/ persistance enabled.

Sorry, I'm attaching the log here ignite_eviction.log I've read https://issues.apache.org/jira/browse/IGNITE-11974 and the thing is, this isn't an infinite loop. The remainingPartsToEvict=$something starts going

Re: Multithread transactions in a C++ Thin Client

I mean, mutex should be taken for the entire transaction of course. Best Regards, Igor On Thu, Jan 14, 2021 at 7:49 PM Igor Sapego wrote: > That's true. We need to implement async reading from client socket to > handle cases like this one properly. Currently as a workaround I can > only

Re: Multithread transactions in a C++ Thin Client

That's true. We need to implement async reading from client socket to handle cases like this one properly. Currently as a workaround I can only suggest guarding the whole client with mutex or create separate clients for threads that do transactional operations. I filed a ticket for the issue [1].

Multithread transactions in a C++ Thin Client

Hello all, We're developing a multithread application using one C++ Thin Client to connect to a cluster with a single Server Node. The C++ Thin Client version is "master" from January 21. We have implemented a "lock-and-update" system based on the "GetAndPut" function and

Re: Query execution is too long

Hi Siva, Have you checked the SQL tuning documentation? https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/sql-tuning - Alex Shapkin -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Ignite rebalancing when a server is rebooted w/ persistance enabled.

Hi, Looks like the error message is truncated. Could you please re-send it or attach the full log file? PartitionsEvictManager is part of rebalancing routine and it clears local data before demanding it from other nodes. Also I see the following JIRA

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

1) My testing shows that CassandraCacheStoreFactory is read from xml config once if the cache name does not exist in Ignite Persistence. It appears that CassandraCacheStoreFactory bean is persisted along with cache name in Ignite Persistence Store, CassandraCacheStoreFactory will not be

Re: Client stuck on startup

Hello! It is possible that Linux is more lenient towards creation of massive number of threads. Regards, -- Ilya Kasnacheev ср, 13 янв. 2021 г. в 19:44, VeenaMithare : > Let me debug this a bit more. Also I will try and capture another set of > thread dumps when this occurs again. This issue

Re: incorrect partition map exchange behaviour

Hello! I have just looked at this issue today, and the relevant fix seems to be https://issues.apache.org/jira/browse/IGNITE-11147 Regards, -- Ilya Kasnacheev ср, 13 янв. 2021 г. в 20:26, tschauenberg : > Sorry about mixing the terminology. My post was meant to be about the PME > and the

Re: 2.8.1 : INFO org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted incoming communication connection

Hello! I am using your reproducer and I did not change dependencies, so I assume it's on 2.8.1 if your reproducer uses it. Yes, I'm running both server and client from the reproducer. Maybe you could record a screencast where you run it and get the result that you describe? Regards, -- Ilya

Re: [External]Re: Exporter usage of Ignite 2.8.0

Hello! This sounds like a correct approach. Regards, -- Ilya Kasnacheev чт, 14 янв. 2021 г. в 15:07, facundo.maldonado : > As far as I know it's not possible to call statically a non-factory > method, a > void method like PrometheusStatsCollector.createAndRegister(). > > I resolved that

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Hello! Looks overall correct. Regards, -- Ilya Kasnacheev чт, 14 янв. 2021 г. в 11:43, xmw45688 : > 1) My testing shows that CassandraCacheStoreFactory is read from xml config > once if the cache name does not exist in Ignite Persistence. It appears > that > CassandraCacheStoreFactory bean

Re: [External]Re: Exporter usage of Ignite 2.8.0

As far as I know it's not possible to call statically a non-factory method, a void method like PrometheusStatsCollector.createAndRegister(). I resolved that creating another bean wrapping the collector and http server creation. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/