ICacheEntryProcessor throws BinaryObjectException when WRITE_SYNCHRONIZATION_MODE=FULL_ASYNC

Hi, We are testing WRITE_SYNCHRONIZATION_MODE=FULL_ASYNC mode to compare performance to PRIMARY_SYNC.These same code works fine in PRIMARY_SYNC, but it throws BinaryObjectException on FULL_ASYNC mode. Would you please recommend any way to fix this issue ?Thanks!*Environment: * ignite 2.6 jdk 8

Map C# class to Cassandra persistence settings

Hello, I am integrating Cassandra to ignite.NET. I followed an example, and managed to make a cache be persisted to Cassandra with primitive data types. https://apacheignite-mix.readme.io/v2.6/docs/examples But is it possible to map C# key/value type classes to the Cassandra persistence

Ignite.NET + Apache Cassandra integration for SQL cache

Hi, We create a cache using SQL DDL syntax. How can I configure Cassandra persistent store to the cache in .NET application ? It seems like default CacheConfiguration is automatically applied internally in Java codes for SQL cache, so not able to load up Spring.XML for that cache. Here is

Re: Ignite graceful shutdown

*1. */> if i call this method, Ignition.Shutdown(null, false); The Ignition class does not contain the `Shutdown` method [1], [2] Perhaps, you mean 'stop'. / -> ah, yes stop method in ignite dotnet C# API. Apache.Ignite.Core.Ignition bool Stop(string name, bool cancel) *2. */> Does the

Ignite graceful shutdown

Hello, We are running many ignite server nodes in windows VM scaleset in a cloud. But sometimes cloud provider forcefully reboot multiple VMs for system update (even though update policy is set to manual, it forces reboot sometimes) Cache mode is partitioned cache with 2 backups. The worst

[TcpCommunicationSpi] Close incoming connection, unknown node

Hi, We have been running ignite v2.5.0 snapshot (2018/5/11) fine for about two weeks. But suddenly, the grid stopped responding with massive infinite log spams, / 2018/05/24 18:56:14.909 [INFO ][grid-nio-worker-tcp-comm-5-#46][TcpCommunicationSpi] Accepted incoming communication connection

Re: Node FAILED

Thanks Anton for the information. Here I re-summarized and added more details and both server and client logs when the incident happened. [Cluster configuration] Windows Azure VM scale set Windows Server 2016 10.0 amd64 VM x 40 nodes VM information: Java(TM) SE Runtime Environment

Re: Node FAILED

jstack dump attached. ignite-jstack.txt -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node FAILED

It seems like ignite server process frozen. The dotnet ignite server process is still alive, but metrics stopped, no other logs, no CPU usage. This is the last error message in ignite server logs. * server log (in attached logfile) 2018/05/10 18:49:56.343 [INFO

Node FAILED

Hi, We are running ignite 2.3 grid in 40 nodes cluster. 1 ignite server, 2 ignite clients per each node. so, total 40 ignite servers 80 ignite clients Topology snapshot [ver=120, servers=40, clients=80, CPUs=640, heap=560.0GB] It runs ok upto about 12 hours uptime, and total partitioned