Ignite 2.9 one way client to server communication

I see that ignite 2.9 has added support for one-way thick-client to server connections. Does it reduce the time taken to connect thick client to server and provides all thick client functionalities? Does client still be in ring? Right now we r facing issues with thick client where it is taking

Re: Execution of local SqlFieldsQuery on client node disallowed

Hi Narges, Then just send a task to a required node. If the cluster topology changes while the task was running you can re-submit it to ensure the result is accurate. - Denis On Fri, Oct 30, 2020 at 2:16 PM narges saleh wrote: > Hi Denis, > > My problem with using affinity call/run is that I

Ignite timeouts and trouble interpreting the logs

First some background. Ignite 2.8.1 with a 3 node cluster, two webserver client nodes, and one batch processing client node that comes and goes. The two webserver thick client nodes and the one batch processing thick client node have the following configuration values: *

Re: Execution of local SqlFieldsQuery on client node disallowed

Hi Denis, My problem with using affinity call/run is that I have to have the key in order to run it. I just want to run a function on the data on the current node, without knowing the key. Is there anyway to do this and also guard against partition rebalancing? thanks On Tue, Oct 27, 2020 at

Re: Apache Ignite talks videos from IMC Summit 2000

Hi Kseniya, Thank you for sharing the videos details, much appreciate it. Regards, Saikat On Fri, 30 Oct 2020 at 12:13 PM, Kseniya Romanova wrote: > Hi, igniters! > Below you can find videos of Ignite talks at the passed Virtual In-memory > Computing Summit: > >1. Apache Ignite Training

Re: Ignite instances frequently failing - BUG: soft lockup - CPU#1 stuck

Looks like it was a centos 8 bug with ksmtuned. Had a few VMs going crazy with cpu for that process. I have disabled that service and CPU on the VM cluster is down. I am going to wait to see if that resolves it. Brian -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Apache Ignite talks videos from IMC Summit 2000

Hi, igniters! Below you can find videos of Ignite talks at the passed Virtual In-memory Computing Summit: 1. Apache Ignite Training Part 1—Setting Up Apache Ignite Management and Monitoring Solution with GridGain Control Centerr—by Denis Magda https://www.youtube.com/watch?v=6R6y7RLT2YA

Re: Tracing configuration

Le vendredi 30 octobre 2020 à 18:03 +0300, Maxim Muzafarov a écrit : > Hello Bastien, > > Is the issue [1] is the same as you faced with? > It seems to me it will be available in 2.9.1 (or 2.10). > > [1] https://issues.apache.org/jira/browse/IGNITE-13640 Hello, It may be, but I don't know

Re: Inserting date into ignite with spark jdbc

Yes I don't want to supply an Ignite Configuration XML I would like to connect through JDBC like any other database. And there is no way to supply the primary key. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

When doing a redeploy of JBoss WAR with Apache Ignite, Failed to marshal custom event: StartRoutineDiscoveryMessage

Also posted on https://stackoverflow.com/questions/64611498/when-doing-a-redeploy-of-jboss-war-with-apache-ignite-failed-to-marshal-custom so please answer there so i can reward with points. I am trying to make it so I can redeploy a JBoss 7.1.0 cluster with a WAR that has apache ignite. I am

Re: Inserting date into ignite with spark jdbc

Denis, I can check it out soon. The mentioned problem can probably only be related to JDBC data frames. In this case, I will create a JIRA ticket. But as I know using OPTION_CREATE_TABLE_PRIMARY_KEY_FIELDS should be the same as I showed in my example. BR, Andrei 10/30/2020 6:01 PM, Denis

Re: Tracing configuration

Hello Bastien, Is the issue [1] is the same as you faced with? It seems to me it will be available in 2.9.1 (or 2.10). [1] https://issues.apache.org/jira/browse/IGNITE-13640 On Fri, 30 Oct 2020 at 17:49, Bastien Durel wrote: > > Hello, > > I'd like to activate tracing to investigate a

Re: Inserting date into ignite with spark jdbc

Andrey, Do we need to update our docs? It feels like the docs miss these details or have an outdated example. - Denis On Fri, Oct 30, 2020 at 7:03 AM Andrei Aleksandrov wrote: > Hi, > > Here's an example with correct syntax that should work fine: > > DataFrameWriter < Row > df = resultDF >

Too long JVM pause out of nowhere leading into shutdowns of ignite-servers

Hello! In our project we are currently using ignite 2.81 and using zookeeper. During the last couple of days we were facing shutdowns of some of our ignite-server nodes. Please find the logs below: 1) Why can there occur such long jvm/gc pauses although previous metrics in the log do not

Tracing configuration

Hello, I'd like to activate tracing to investigate a slowdown, I have succeeded (I think) to activate trace gathering by linking optional/ignite-opencensus/ into libs, then using control.sh Command [TRACING-CONFIGURATION] started Arguments: --tracing-configuration

Re: Ignite Cluster Issue on 2.7.6

Hi, Did you remove the code with ignite.cluster().active(*true*); ? However, yes, all of your data nodes should be in baseline topology. Could you collect logs from your servers? BR, Andrei 10/30/2020 2:28 PM, Gurmehar Kalra пишет: Hi, I tried changes suggested by you , waited for nodes  

Re: IgniteSpiOperationTimeoutException: Operation timed out [timeoutStrategy= ExponentialBackoffTimeoutStrategy

Hi, Often, problems with establishing a communication connection can be solved with the following configuration: 1)You may have multiple network interfaces and the wrong one could be used. Solved by changing the SPI communication timeouts.:    

Re: Ignite instances frequently failing - BUG: soft lockup - CPU#1 stuck

Hello, Too little information has been provided on your part: 1) Could you provide the screenshot from the web console at this time? 2) Could you collect Ignite logs during this period? 3) What tool shows that the processors are frozen? Have you checked other tools? BR, Andrew 10/30/2020

Re: Inserting date into ignite with spark jdbc

Hi, Here's an example with correct syntax that should work fine: |DataFrameWriter < Row > df = resultDF .write() .format(IgniteDataFrameSettings.FORMAT_IGNITE()) .option(IgniteDataFrameSettings.OPTION_CONFIG_FILE(), configPath) .option(IgniteDataFrameSettings.OPTION_TABLE(), "Person")

Ignite instances frequently failing - BUG: soft lockup - CPU#1 stuck

Ignite instances keep failing. Server indicates CPU stuck. However monitoring shows very little CPU usage. This happens almost every day on different nodes of the cluster. -- Sent from:

RE: Ignite Cluster Issue on 2.7.6

Hi, I tried changes suggested by you , waited for nodes and then tried to start cluster , but only 1 node is joins cluster other node does not participates in cluster. Do I have to add all nodes into BLT ? Regards, Gurmehar Singh From: Andrei Aleksandrov Sent: 29 October 2020 20:11 To:

Re: IgniteSpiOperationTimeoutException: Operation timed out [timeoutStrategy= ExponentialBackoffTimeoutStrategy

Hello! Do you have a reproducer for this behaviour that I could run and see it failing? Regards, -- Ilya Kasnacheev вт, 27 окт. 2020 г. в 22:02, VeenaMithare : > Hi Ilya, The node communication issue is because one of the node is being > restarted - and not due to network failure . The

Re: Client App Object Allocation Rate

Hello! I guess that you have EVT_NODE_METRICS_UPDATED event enabled on client nodes (but maybe not on server nodes) It will indeed produce a lot of garbage so I recommend disabling the recording of this event by calling ignite.events().disableLocal(EVT_NODE_METRICS_UPDATED); + dev@ Why do we

Re: removing ControlCenterAgent

Le jeudi 29 octobre 2020 à 12:07 +, Mekhanikov Denis a écrit : > Hi! > > The issue is that Control Center Agent puts its configuration to the > meta-storage. > Ignite has an issue with processing data in meta-storage with class > that is not present on all nodes: >

Re: High availability of local listeners for ContinuousQuery or Events

Hi Igor, We hope that if the local listener node fails, we can have a mechanism similar to fail over. Otherwise, if the local listener node fails and restarts, the events during the failure will be lost. 在 2020/10/30 上午12:04, Igor Belyakov 写道: Hi, In case the node, which registered a