Re: Only one node has a high number of SystemExecutor CompletedTask

I found something that could be a clue. The node exposed by ignite.cluster().forServers().forOldest().node() seems to be a problem. Do you have any expectations? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Only one node has a high number of SystemExecutor CompletedTask

The pattern we use is a structure that periodically creates and destroys Cache. At this point, could a particular node not be able to clean up the heap? -- Sent from:

Only one node has a high number of SystemExecutor CompletedTask

Hi, team. I have a problem about cluster cpu usage. Ignite Cluster is running on 10 nodes. Unusually, only one node has a high number of SystemExecutor and CPU utilization and Minor GC time are higher than other nodes. Is there a separate role between the nodes, so that one node becomes the

Error when deploying a service into an Ignite cluster

I have made a simple C# service in Ignite 2.2. When I deploy it, like this: services.DeployNodeSingleton(“AddSurveyedSurface”, new AddSurveyedSurfaceService()); I get the following error: ERROR 2017-11-13 15:29:35,984 319109ms GridServiceProcessor ?

Problem with spring-data-commons 2

Hi Using the following versions: spring-data-commons = 2.0.0.RELEASE ignite-spring-data = 2.3.0 I receive the following error trying to use an IgniteRepository: Error:(8, 8) java: name clash: deleteAll(java.lang.Iterable) in org.springframework.data.repository.CrudRepository and

Adding more ignite-clients slows down the first client

Hi I try to achieve very high inserts with Ignite-Cassandra I have done some extensive testing, measuring all kinds of stuff So long story short, here is my conclusion, I see the following when measuring INSERT rate per client As you can see the first ignite-client has ~19,000 INSERTs / second

[Ignite 2.0.0] Stopping the node in order to prevent cluster wide instability.

Hi team, I have a problem about Ignite Cluster. Nodes die in 10 hour increments, leaving the following logs: And, when a cluster is configured, only one node is used at a high rate. This part seems to have some influence. The log when an issue occurs is shown below.