Re: How to do address resolution?

Thanks, John. That connectivity improvement fixes situations when a server needs to open a connection to a client but fails. The client will be opening the connection instead after getting a special message via the discovery networking layer. It won’t improve the communication between Visor and

Re: How to do address resolution?

Sorry, mixed the thread, it the one that asks if server nodes connect back to thick clients and it was you who mentioned the new feature... On Wed., Jul. 1, 2020, 4:03 p.m. John Smith, wrote: > If you look for the "what does all partition owners have left mean?" > thread. > > There is mention

Re: How to do address resolution?

If you look for the "what does all partition owners have left mean?" thread. There is mention to improve the protocol so that other nodes don't need to connect to clients running inside containers... It links to another thread indicating that there may be a PR to add a flag of some sort to mark

Re: How to do address resolution?

> > But you guys also mentioned in my other thread that you are working on a > feature that doesn't require connecting to the client when it's running > inside a container. What is the tread you're referring to? Visor always will be connecting to the clients regardless of your deployment

Re: How to do address resolution?

Hi, yes I figured that visor is just another thick client. By using address resolver on my thick client applications inside container everything works fine and visor also connects properly (no need to add all client configs everywhere). As stated it just adds tiny delay when visor needs to

Re: Setting Cache Size using Max Records

1. There is no any public API for that but you can follow a workaround suggested here . If you have a POJO class of your domain object, then create an instance, convert it to BinaryObjectImpl and get the array size (as

Re: ScanQuery Transform: fail to deserialze! ignite 2.8.0, java 11

Hi Rafael, Lamdas and anonymous classes capture and serialize their Inner/OuterClass with all the fields, and classes of the fields of those fields, etc. In your case, ScanQueryClass was captured during the lamda serialization and that class was not found during deserialization on the other side:

Re: How to do address resolution?

Hi John, As Stephen mentioned, Visor connects to the cluster in a way similar to server nodes and thick clients. It's connected as a daemon node that is filtered out from metrics and other public APIs. That's why you don't see Visor being reported in the cluster topology metrics along with

ScanQuery Transform: fail to deserialze! ignite 2.8.0, java 11

Hey Guys, I have a strange problem with the Transform part of a ScanQuery that I get a deserialize object exception for the SerializedLambda. > javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: > Failed to deserialize object [typeName=java.lang.invoke.SerializedLambda]

Re: How to do address resolution?

It’s not that Visor connects to a thick client, it’s that it is a thick client. There are some weird implementation details — like it’s written in Scala and using “daemon mode” — but it becomes part of the cluster, so the same “rules” apply as any other thick client. Connections to other nodes

Re: How to do address resolution?

So this is what I gathered from this experience. When running commands on Visor's console, Visor will attempt to connect to the thick client. For example if you type the "node" command and attempt to get detailed statistics for a specific thick client, Visor will pause on the data region stats

Re: Blocked system-critical thread has been detected - After upgrade to 2.8.1

Manu, Can you set up the lightest load/simplest topology possible, send the Ignite logs from all nodes(server and clients), including the GC logs, and we will take a look. https://apacheignite.readme.io/docs/jvm-and-system-tuning#detailed-garbage-collection-stats Thanks, Alex -- Sent

Re: CusterGroup topology unexpectedly empty

Using ignite reference is completely fine. What is the exact exception being thrown in this case? I would expect to see this if the node is out of topology, what does the logs tell? Do other nodes see this one in the topology? Please check if there are NODE_FAILED events for the node on other

Re: Ignite node log file setup

Hello, I'm waiting for reply :) How can I set system property to use in ignite config file?? I set and got a error so , attacted log file before.. Thank you so much -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

CusterGroup topology unexpectedly empty

I've been researching a problem where we see a ClusterGroup topology becoming unexpectedly empty. I have not found anything that is similar to my case outlined below: We have some code using the C# client on Ignite 2.8.0 like this: var _group = _ignite?.GetCluster()?.ForAttribute(_roleAttribute,

Re: Blocked system-critical thread has been detected - After upgrade to 2.8.1

Hi Alex, thanks so much. We are reduced topology to picture below (1 server node and 3 clients). - 1 Ignite server node: IMDB with persistence enabled - 3 Ignite client nodes: for SQL query, messaging (topic, queue) and countdown latches. All pluggable elements (TOPIC listener and QUEUE