Cluster freeze with SSL enabled and JDK 11

Hello, I can consistently reproduce this issue with Ignite 2.6.0, JDK 11 and SSL enabled: - the second node that I bring up joins, and then shortly after freezes and prints this message every minute: "WARN ...[*Initialization*] processors.cache.GridCachePartitionExchangeManager: Still

RE: IO implications of ScanQuery

Hi Ilya, Thanks for the clarification. I assume this not the case if the cache is represented as an SQL table as the SQL table will construct a primary key from the entire key of the ICache cache. Shifting the question a little, if the keys are serialized via a raw IBinarizable interface

Re: Cluster is not responsive after node segmentation and reconciliation

Another interesting piece - sudden ClassNotFoundException - it obviously works in a steady state. ignite-cluster-pairs.log -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cluster is not responsive after node segmentation and reconciliation

Understood. Those logs are pretty lengthy, let me bring some interesting pieces here. I can separate this part, with communication errors and out of memory ignite-cluster-oom.log -- Sent from:

Cannot query cache by affinity key when custom cache template is used

I am crossposting this from StackOverflow. I noticed that when I query a cache which was created with a custom cache template and include the cache's affinity key in the WHERE clause, no results are returned. I am running Ignite 2.5 with the following configuration:

Re: Is it possible to avoid redeployment of an Ignite service n a cluster even if the node bound to it gets down?

Hello! I think that you should use compute or lifecycle listener in place of service for such scenario. Service is something that needs to be deployed continuously. Regards, -- Ilya Kasnacheev чт, 18 окт. 2018 г. в 13:13, the_palakkaran : > Hi, > > I have a cache loading service in an

zookeeper jd(joindata) never delete

ignite version 2.5.0 discovery spi: ZookeeperDiscoverySpi when I start a client node c. c can join the cluster. but c just join the cluster never call any cache method. the jd path children willl never deleteed: -- Sent

Is it possible to avoid redeployment of an Ignite service n a cluster even if the node bound to it gets down?

Hi, I have a cache loading service in an ignite cluster. Since cache loading is expected to be a one time activity, is it possible to avoid a redeployment if the node bound to it gets down? If it gets deployed again, it will load cache again, which is not expected. PS: I have a work around to

Re: Writing binary [] to ignite via memcache binary protocol

Hello! It will just take two first bytes from extras and turn them into a numeric variable. Later on, if flags & 0xff00 == 0x100b, then it is byte array, else it is string. You should find a way to make your implementation send '-128' as fourth byte (If I understand endianness correctly).

Re: IO implications of ScanQuery

Hello! As far as my understanding goes, Keys are stored alongside Values in Durable Memory pages, and they are likely both pulled from pages on scan query. This means the latter explanation is closer to reality. Regards, -- Ilya Kasnacheev ср, 17 окт. 2018 г. в 23:05, Raymond Wilson : > I

Re: close method must be called on IgniteCache?

Hello! I think you should avoid calling close() on Ignite caches. If you want to delete cache with all data, call destroy(). If you don't, just leave the IgniteCache object as is. It will be stored in Ignite internals and given back to you for further operations. Regards, -- Ilya Kasnacheev

Re: Adding entry to partition that is concurrently evicted

Hi, Could you please attach the configuration of the cluster and full log? BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

close method must be called on IgniteCache?

here is the document from source code I just wondering is the `close` method must be called ? for my case, In my kafka consumer, I did some computation and then put the data into ignite. as the message comes in continuous, I just wondering if keep `close` and `open` frequently will decrease the

Re: Writing binary [] to ignite via memcache binary protocol

Hi, Thanks for pointing out the mistake about the string data type. I used python3 which supports bytes type and run the test case. Ignite would seems still treat the received value as String type and would decode the data correctly. I would like to try with a some simple C client program and see

Re: Apache Ignite 2.6.0 JDBC Thin Client Multiple Endpoints Issues

Hi, Thanks for pointing out the mistake. After correcting, the issue as resolved. Arpit -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Adding entry to partition that is concurrently evicted

Hi guys, I was using ignite in cluster mode with SQL. Yesterday, when I was trying to add more node into existed cluster nodes, an error occurred and the whole cluster seems done. Error logs shows below. Any idea what should I do to avoid this error again? Thanks a lot.