RE: Ignite 2.10 post upgrade concerns

Hi Igniters, Can anyone guide on this please ? Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 17 September 2021 11:26 To: user@ignite.apache.org Subject: Ignite 2.10 post upgrade concerns Hi Igniters, We recently upgraded to Ignite 2.10 from 2.7.6, where we observed below issues

Ignite 2.10 post upgrade concerns

(using warm-up feature). Is there any alternative where we can pass only selective list of caches for warm-up? Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be pr

RE: [External]Re: Client taking long time to connect to cluster

Yohan, we have tried with JVM param as well, still its taking long time to connect. Thanks and Regards, Kamlesh Joshi From: Yohan Fernando Sent: 02 September 2021 15:00 To: user@ignite.apache.org Subject: Re: [External]Re: Client taking long time to connect to cluster The e-mail below is

RE: [External]Re: Client taking long time to connect to cluster

Hi Yohan, We have already added this but not as a JVM param but via a code, like setting in system properties. Still the issue persists. Any other work around? Thanks and Regards, Kamlesh Joshi From: Yohan Fernando Sent: 02 September 2021 14:44 To: user@ignite.apache.org Subject: [External

Client taking long time to connect to cluster

ne unix 3 [ ] STREAM CONNECTED 142112733 38647/bwengine unix 3 [ ] STREAM CONNECTED 142148802 38647/bwengine unix 3 [ ] STREAM CONNECTED 142112732 38647/bwengine Any pointers on this would be helpful. Thanks and Regards, Kamlesh Joshi "Confiden

How to add a support for encryption/decryption of third party persistence password

file: Property file entry: thirdPartyDS.jdbc.password=ENC(AQqqmNSRdDQDic+9nMnFRq5rrkQZn) Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This messa

Conditional data Preloading from third party persistence

Sending again to reflect in portal ! Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 21 June 2021 17:25 To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Conditional data Preloading from third party persistence Hi Igniters, Am trying to preload certain dat

FW: Conditional data Preloading from third party persistence

Sending again to reflect in portal ! Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 21 June 2021 17:25 To: user@ignite.apache.org Subject: Conditional data Preloading from third party persistence Hi Igniters, Am trying to preload certain data from third party persistence, but am

Conditional data Preloading from third party persistence

gnite-core-2.7.6.jar:2.7.6] at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_271] ... 3 more Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are c

RE: Ignite nodes crash after firing heavy SQL query

. sqlQueryMemoryQuota 2. sqlOffloadingEnabled 3. sqlGlobalMemoryQuota Thanks and Regards, Kamlesh Joshi From: Craig Gresbrink Sent: 26 May 2021 21:17 To: user@ignite.apache.org Subject: [External]RE: Ignite nodes crash after firing heavy SQL query The e-mail below is from an external source. Please

Ignite nodes crash after firing heavy SQL query

le to kill such queries ? 2. Any way to set SQL query timeout at cluster level? 3. Any parameters that we should be tweaking to avoid this? Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended rec

RE: Unable fetch Ignite JMX metrics

Hi Team, Any update on this please ? Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 13 May 2021 13:11 To: 'user@ignite.apache.org' Subject: RE: Unable fetch Ignite JMX metrics Hi Igniters, After getting the latest source code of JMX exporter, below mentioned issue (

RE: Unable fetch Ignite JMX metrics

:682) ... 3 more Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 11 May 2021 19:57 To: user@ignite.apache.org Subject: Unable fetch Ignite JMX metrics Hi Igniters, We have recently upgraded to ignite 2.10.0. Post upgrade, unable to fetch the metrices using JMX exporter

Unable fetch Ignite JMX metrics

) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s).

RE: [External]Re: Cluster becomes unresponsive if multiple clients join at a time

Thanks Ilya! I have observed PME related log entries in latest version as well. Does this mean these ‘some conditions’ are not met? Can you elaborate on this please ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: 22 April 2021 16:24 To: user@ignite.apache.org Subject: Re

RE: [External]Re: Cluster becomes unresponsive if multiple clients join at a time

Hi Ilya, Yeah even that’s what we were suspecting, PME triggering might be causing issue. We are using 2.7.6 version. So you are saying, in recent version i.e. 2.10.0 version don’t have blocking global PME ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: 21 April 2021 20:12

Cluster becomes unresponsive if multiple clients join at a time

? Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmi

RE: [External]Re: Ignite PME query

Hi, I couldn't get the exact details what am looking for, that's why am writing here again. Can anyone please enlighten me on below points ? Thanks and Regards, Kamlesh Joshi -Original Message- From: VeenaMithare Sent: 01 March 2021 13:55 To: user@ignite.apache.org Subject:

RE: Ignite PME query

HI Igniters, Can anyone update on this please? Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 25 February 2021 19:59 To: user@ignite.apache.org Subject: Ignite PME query Hi Igniters, I have below queries, can anyone please comment on these: 1. Whenever any thick client joins

Ignite PME query

set to INFO) Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any revie

RE: [External]Re: removeAll operation on same cache causing deadlock

Ohh! Anyways thanks for the update ! Regards, Kamlesh Joshi From: Alex Plehanov Sent: 21 January 2021 13:20 To: user@ignite.apache.org Subject: [External]Re: removeAll operation on same cache causing deadlock The e-mail below is from an external source. Please do not open attachments or

removeAll operation on same cache causing deadlock

rrent removeAll() on the same cache" this has been fixed. However, we were still able to reproduce the issue in this version as well. Can anyone please validate this? Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for

partition-exchanger system-critical thread blocked

concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the

RE: [External]Re: Usage of TransactionConfiguration to overcome deadlocked threads

Thanks for the update Alex. Actually we are using BinaryObjects for such operations. Is there any implementation available (or a reference) to sort user defined types of objects ? Thanks and Regards, Kamlesh Joshi From: Alex Plehanov Sent: 20 October 2020 19:54 To: user@ignite.apache.org

Usage of TransactionConfiguration to overcome deadlocked threads

, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard

RE: [External]Re: Failed to process selector key frequently at client side

a Kasnacheev пт, 9 окт. 2020 г. в 09:37, Kamlesh Joshi mailto:kamlesh.jo...@ril.com>>: Hi Igniters, We have three server nodes, there is firewall between clients and servers. Opened 47500 and 47100 series ports, but still below errors are printing at client side frequently. But client a

Failed to process selector key frequently at client side

org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) [ignite-core-2.7.0.jar:2.7.0] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_151] Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use o

RE: [External]Re: how to achieve timeout for get/put/remove operations

our own timeouts and use getAsync API that is the only way we can achieve this (as we are not using any transactions). Thanks and Regards, Kamlesh Joshi From: Stephen Darlington Sent: 22 September 2020 18:11 To: user@ignite.apache.org Subject: Re: [External]Re: how to achieve timeout for get

RE: [External]Re: how to achieve timeout for get/put/remove operations

Thanks ilya. Does that mean, we have to specifically maintain a time counter and act accordingly on it? I was hoping, if there is any API where we could just pass timeout value as well, as a parameter and Ignite would handle internally. Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev

how to achieve timeout for get/put/remove operations

Hi Igniters, How to achieve/get timeout error for particular operation (get/put/remove), if it crosses certain timeout value then I can take certain action based on that. Is there any Ignite API readily available for this? Any pointers would be helpful ! Thanks and Regards, Kamlesh Joshi

RE: [External]Re: Private network setup for server nodes in ignite cluster

Thanks for the update Ilya. You mean in this scenario, thin clients will work properly (will be connecting via public IP instead of private). And do you have any idea when Ignite 2.9 version will be released ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: 07 September 2020 19

RE: [External]Re: Private network setup for server nodes in ignite cluster

Hi Ilya, Any updates on this please? Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 04 September 2020 17:33 To: user@ignite.apache.org Subject: RE: [External]Re: Private network setup for server nodes in ignite cluster Hi Ilya, We have tried the setup by putting public ips for

RE: [External]Re: unable to start node

Denis, Did u got any chance to go through this? Please update if you have.. Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 03 September 2020 19:54 To: user@ignite.apache.org Subject: RE: [External]Re: unable to start node Denis, Below is the cache config. We have used Binary

RE: [External]Re: Private network setup for server nodes in ignite cluster

. Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: 18 August 2020 16:05 To: user@ignite.apache.org Subject: [External]Re: Private network setup for server nodes in ignite cluster The e-mail below is from an external source. Please do not

RE: [External]Re: unable to start node

Denis, Below is the cache config. We have used Binary Objects as well from some of thick clients to update cache. [cid:image001.png@01D6822B.29DF8F50] Thanks and Regards, Kamlesh Joshi From: Denis Mekhanikov Sent: 03 September 2020 18:33 To: user Subject: Re: [External]Re: unable to start

RE: [External]Re: unable to start node

Denis, Yes, we do have table connected to that cache (we don’t update anything though SQL though) but its not created via CREATE TABLE command. We use XMLs to create caches. Thanks and Regards, Kamlesh Joshi From: Denis Mekhanikov Sent: 03 September 2020 16:35 To: user Subject: Re

RE: [External]Re: unable to start node

issue earlier (in version 2.6.0). We migrated to Ignite 2.7.6 around 3 months back. Please, let me know is there anything we should try to recover the node ? Thanks and Regards, Kamlesh Joshi From: Denis Mekhanikov Sent: 03 September 2020 14:08 To: user Subject: Re: [External]Re: unable to

Re: [External]Re: unable to start node

open attachments or click links from an unknown or suspicious origin. Kamlesh Joshi wrote: > */[2020-08-28T19:05:03,296][ERROR][sys-#940187%EDIFReplica%][] JVM will > be halted immediately due to the failure: [failureCtx=FailureContext > [type=CRITICAL_ERROR, err=org.h2.message.Db

RE: [External]Re: Node left from running cluster due to org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException: Runtime failure on search row

Thanks for the update Andrei. We upgraded from 2.6.0 to 2.7.6. We followed the same approach and it worked properly. Can we change INLINE SIZE for every cache at runtime ? Thanks and Regards, Kamlesh Joshi -Original Message- From: aealexsandrov Sent: 27 July 2020 19:35 To: user

Node left from running cluster due to org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException: Runtime failure on search row

NUMBER:491190045, null, null, null, 2017-08-12 16:01:50.399, NO00FBVT ]" [5-197]]] Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If

RE: [External]Re: Ignite cluster became unresponsive

Thanks for the findings Ilya. So shall we set the same timeout value for socketWriteTimeout as that of failure detection timeout on both client and server side? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: 10 July 2020 19:48 To: user@ignite.apache.org Subject: Re: [External

RE: [External]Re: Ignite cluster became unresponsive

Hi Stephen/Team, Did you got any chance to look into this? Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: 06 July 2020 14:50 To: user@ignite.apache.org Subject: RE: [External]Re: Ignite cluster became unresponsive Hi Stephen, We have started our node with below JVM parameters

RE: [External]Re: Ignite cluster became unresponsive

that we encountered right? Correct me if am wrong. Thanks and Regards, Kamlesh Joshi From: Stephen Darlington Sent: 06 July 2020 14:09 To: user Subject: [External]Re: Ignite cluster became unresponsive The e-mail below is from an external source. Please do not open attachments or click links

Ignite cluster became unresponsive

ommunicationSpi] Communication SPI session write timed out (consider increasing 'socketWriteTimeout' configuration property) [remoteAddr=/xx.xx.xx.xx:42190, writeTimeout=2000] Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only fo

RE: [External]Re: Segregating Ignite client discovery and heartbeat exchange on different networks

Thanks Alex. Actually, I don't want to start two different clusters on same machine, rather am looking to have a different networks for Ignite clients discovery and internal communication. Not sure whether we can achieve this using below. Thanks and Regards, Kamlesh Joshi -Ori

Segregating Ignite client discovery and heartbeat exchange on different networks

Hi Igniters, Is there any way, we can separate out Ignite client discovery and cluster internal communication (heart beat exchange and PME) on two different networks (may be by using 2 Ethernet cards) ? Currently, we are using TcpDiscoveryVmIpFinder. Thanks and Regards, Kamlesh Joshi

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

/ will it be exposed on some default port (likewise ignite-rest)? How does exactly opencensus will affect the cluster? Thanks and Regards, Kamlesh Joshi -Original Message- From: akurbanov Sent: 24 March 2020 19:28 To: user@ignite.apache.org Subject: [External]Re: Exporter usage of

Exporter usage of Ignite 2.8.0

? So that these exporters then can directly be consumed by Prometheus. Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended

Unable to connect to Ignite Visor Console in Ignite 2.8.0

around it? Ignite 2.8.0 docs are not available on the site ! $IGNITE_HOME/bin/ignitevisorcmd.sh -cfg="/app/Ignite/visorconfig.xml" [cid:image001.jpg@01D5F312.05CC1780] Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended on

exposing Ignite cluster health status in microservices

appreciated ! Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmi

JVM metrics for Prometheus are not getting populated for Ignite 2.6.0

metrics are produced properly. Not sure why there is a difference between these 2 versions? is this a defect or am I missing something? Any pointers on this are appreciated ! Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only fo

RE: [External]Re: Freeing up RAM/cache

Thanks for the response Denis ! That answers my one question. Could you please suggest on below question regarding expiration policy ? Thanks and Regards, Kamlesh Joshi From: Denis Mekhanikov Sent: Thursday, October 10, 2019 10:31 PM To: user@ignite.apache.org; user@ignite.apache.org Subject

Freeing up RAM/cache

policy at the runtime or do we need to re-create the caches? Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient.

RE: [External]Re: Is there any way to force recover the cluster - copying running cluster datastore

Thanks Ilya, will give it a try ! Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: Friday, June 14, 2019 8:40 PM To: user@ignite.apache.org Subject: Re: [External]Re: Is there any way to force recover the cluster - copying running cluster datastore The e-mail below is from an

RE: [External]Re: Is there any way to force recover the cluster - copying running cluster datastore

Hi Ilya, WAL markers you mean cp folder inside datastore ? or any other ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: Friday, June 14, 2019 6:59 PM To: user@ignite.apache.org Subject: Re: [External]Re: Is there any way to force recover the cluster - copying running cluster

RE: [External]Re: Is there any way to force recover the cluster - copying running cluster datastore

Hi Denis, Only WAL disk is corrupted but datastore is intact by any way can we restore the cluster ? some data loss is fine. Any suggestion on this? Thanks and Regards, Kamlesh Joshi From: Kamlesh Joshi Sent: Thursday, June 6, 2019 7:52 PM To: user@ignite.apache.org Subject: RE: [External]Re

RE: [External]Re: Is there any way to force recover the cluster - copying running cluster datastore

Thanks for the update Denis. If one of the WAL disk gets failed, is there any way to start or recover the cluster forcefully ? Thanks and Regards, Kamlesh Joshi From: Denis Magda Sent: Thursday, June 6, 2019 4:44 PM To: user@ignite.apache.org Subject: [External]Re: Is there any way to force

Is there any way to force recover the cluster - copying running cluster datastore

forcefully? This scenario may also arrive if WAL disk gets failed. How can we atleast start the cluster with minimum data loss ? Any help would be highly appreciated ! Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended on

RE: [External]Re: Read/query TPS is decreasing after enabling mix load i.e. write services

or it will really help ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: Monday, May 27, 2019 7:49 PM To: user@ignite.apache.org Subject: Re: [External]Re: Read/query TPS is decreasing after enabling mix load i.e. write services The e-mail below is from an external source. Please

RE: [External]Re: Read/query TPS is decreasing after enabling mix load i.e. write services

Hi ilya, We tried with LOG_ONLY and BACKGROUND both but still behavior remains same. Any other parameter tweak which would help? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev Sent: Wednesday, May 22, 2019 9:14 PM To: user@ignite.apache.org Subject: Re: [External]Re: Read/query TPS

RE: [External]Re: Read/query TPS is decreasing after enabling mix load i.e. write services

Hi Ilya, Looking at the logs, every time checkpoint starts due to ‘timeout’ reason not because the buffer is full. So still do we need to increase checkpointing buffer or only changing checkpointing frequency will help ? Thanks and Regards, Kamlesh Joshi From: Ilya Kasnacheev

RE: [External]Re: Read/query TPS is decreasing after enabling mix load i.e. write services

Hi, Unfortunately, I cant share the reproducer. We are using Ignite Binary Objects for performing operations on the cluster (Get/Put). We have exposed these operations to other application (i.e. TIBCO BW services) which performs operations on the cluster. Thanks and Regards, Kamlesh Joshi

Read/query TPS is decreasing after enabling mix load i.e. write services

this the expected behavior? Or we can change this by using different thread pools ? Kindly help ! Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If y