Re: Regarding Connection timed out observed during client startup

Hi Ilya, >>Generally a reducer node will need to connect to all map nodes while doing SQL query. >>You will not see this message if connection was already up. *Here are examples of 'outgoing communication' when the count was incorrect : *Example 1 : 2021-01-15T17:04:35,905 INFO

[2.7.6] Question about BinaryObject/SQL schema

Hello everyone. I'm creating a partitioned cache with persistence enabled. I use java's thin client to connect my app to ignite. I have a pool of reusable connections, as suggested in the documentation since IgniteClient isn't thread safe. After the cache is created, I'm using SQL "ALTER TABLE"

Re: Regarding Connection timed out observed during client startup

Hello! Generally a reducer node will need to connect to all map nodes while doing SQL query. You will not see this message if connection was already up. Regards, -- Ilya Kasnacheev вт, 26 янв. 2021 г. в 17:11, VeenaMithare : > Hi Ilya, > > >>I don't think it could have affected CQ initial

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

The cluster was almost idle. It didn't receive lots of updates while that node was down. Is there any way to confirm which of those two options you mentioned was executed? Is there any way to configure a threshold to choose one of those two options? -- Sent from:

Re: Regarding Connection timed out observed during client startup

Hi Ilya, >>I don't think it could have affected CQ initial query, since queries/cache operations are supposed to block until they are successful, but not fail silently. I have another observation related to this

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

Hello! While the node was down, the partitions that it previously owned had their data updated. At this point we only have two options: - Throw out existing partitions and rebalance them. AFAIK it involves WAL so it will take some time. I have heard that if you wipe node's persistence then it

Re: Regarding Connection timed out observed during client startup

Hello! I don't think it could have affected CQ initial query, since queries/cache operations are supposed to block until they are successful, but not fail silently. I'm not sure about connectTimeout, please try it and see. The main factor is that you expect your transactions to finish

[2.9.1]in SYS.METRICS View some data is always 0

Hi, We found that SYS.METRICS View some data is always 0, such as QueryCompleted,QueryExecuted,QuerySumTime,QueryCompleted,QuerySumTime and QueryMaximumTime. This is a bug? Or what configuration is needed? Or the related functions have not been implemented yet?