What's the difference between ClientCache#removeAll() and ClientCache#clear()

Here is the code snippet from org.apache.ignite.client.ClientCache what's the difference between these two methods? * /** * Clears the contents of the cache. */ public void clear() throws ClientException; /** * Rem

Re: waiting for partition map exchange questions

Hi Andrei, have you had a chance to check out these logs? Thanks On Sun, Apr 14, 2019 at 17:18 scottmf wrote: > ignite.tgz > > (attached file) > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Ignite DataStreamer Memory Problems

Here is a reproducible example of the DataStreamer memory leak: https://github.com/kellanburket/ignite-leak I've also added a public image to DockerHub: miraco/ignite:leak This can be run on a machine with at least 22GB of memory available to Docker and probably 50GB of storage between WAL and pe

Re: What happens when a client gets disconnected

According to some of our historical metrics, the blocking looks to have been approximately a minute but the granularity of that monitoring is not super precise so I don't have an exact time. I can try to go back to our logs and see if I can determine a more accurate period of time. How does near

Re: Failover in thin client mode

Thank your information very much! Thanks, Ken Cheng On Fri, Apr 26, 2019 at 12:32 AM Igor Sapego wrote: > The point of "Best effort" is that we do not guarantee every requested > to be routed to the optimal node, we only apply our best effort to make > this happen. > > No, cluster will NOT ret

Re: Failover in thin client mode

The point of "Best effort" is that we do not guarantee every requested to be routed to the optimal node, we only apply our best effort to make this happen. No, cluster will NOT return a address list to the client upon handshake because. 1. It may be not secure to connect to nodes, which user did

Re: Failover in thin client mode

I am still on the design phrase of go thin client. once it's ready I will share the link. thanks. Thanks, Ken Cheng On Thu, Apr 25, 2019 at 10:02 PM Igor Sapego wrote: > Hello, > > Are you developing a Go thin client? Can you share a link? > > There is already one go client I'm aware of [1], is

Re: Failover in thin client mode

Not sure my understanding is correct or not. There is the case when a new node join a cluster, if it's just as your said then some key can not get directly from *the new added node* I suppose it would work as below. 1: 5 node cluster(a,b,c,d,e) 2: even I just set two nodes/endpoints in the clien

Re: Failover in thin client mode

with IEP-23 there is a change 1. Tries to establish connection to hosts, which is not yet connected. This is required as changes of the topology may be caused by the new node joining the cluster. Thanks, Ken Cheng On Thu, Apr 25, 2019 at 10:02 PM Igor Sapego wrote: > Hello, > >

data loss during rebalancing when using invokeAsync + EntryProcessor

Greetings, we've been chasing a weird issue in a two node cluster for few days now. We have a spring boot application bundled with an ignite server node. We use invokeAsync on TRANSACTIONAL PARTITIONED cache with 1 backup. We assume that each node in the two node cluster has a copy of the oth

Re: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

Hello! Yes, I can reproduce this scenario. I attribute it to async/await, where there is a .Net callback which is invoked from cache operation and which calls cache operations, and this leads to attempts of scheduling striped pool operations to same stripe as cuirrently occupied. Pavel, what do

Re: Failover in thin client mode

Hello, Are you developing a Go thin client? Can you share a link? There is already one go client I'm aware of [1], is yours related somehow? As for your question, thin client is given list of IPs and ports by a user. During the start, or in background thin client tries to establish connection to

Re: Node joining didn't trigger Affinity recalculation problem

Hi Denis, I just found an issue with the ec2 tcp discovery. If I have one node running in elb and launch a new node in elb, they will join the same cluster properly. However, if I launch two nodes separately first without joining elb and then add them into the same elb after they are fully running

RE: [EXTERNAL] Re: Replace or Put after PutAsync causes Ignite to hang

Hi, is anyone else seeing this or able to reproduce? Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: What happens when a client gets disconnected

Hello! "threads on all the other clients block for a period of time" - how long is this period of time? It definitely makes sense to try more recent version of Ignite. The thread dump that you have shown should be only waiting for all data nodes, which usually are server nodes, so it's not obvio

Re: Failover in thin client mode

Thank your information very much! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failover in thin client mode

Hi, I believe that this paragraph describes what you want to see: Updating partition mapping It is important for client to keep partition mapping updated. To ensure this, the following changes are proposed: 1. Changes in Standard Message Response header. It is proposed to add flag to every

Re: critical thread has been detected

Could you share logs from client nodes? I believe we can find more useful information there. Also, could you share a full log file, not a console output? Or, alternatively, you can run Ignite with -DIGNITE_QUIET=false to enable INFO logging for console output. Evgenii чт, 25 апр. 2019 г. в 00:19,