Re: Thin Client Kubernetes discovery

Max, That improvement automates the cluster discovery if both the cluster and thin clients are deployed *inside* of Kubernetes. That's my reading of the ticket's description. While you're referring to the case when the client is deployed outside of a K8S environment. @Vladimir Pligin , could you

Re: Deploying an app to an ignite cache cluster

Apache Ignite allows you to store the most frequently accessed data in memory. It evenly distributes the data across a cluster of computers in either partitioned or replicated manner. Ignite allows you to access the data from any underlying data store – RDBMS, NoSQL, or HDFS. you can dynamically

Thin Client Kubernetes discovery

Hi, Igniters I'm now discovering the issue https://issues.apache.org/jira/browse/IGNITE-13204 and wondering what is a case that requires a client to be able to discover a cluster? I believe that discovery is a goal of kubernetes itself. We could assign a DNS name for a Service [1] and then any

Re: Apache Ignite 3.0

Hi Petr, Got it, that makes sense. I think we should rely on Maven for this. Basically, like the mvnw wrapper, but specific for Ignite purposes (enable/disable a module, start/stop a node, etc.). BTW, do you think RPM/DEB packages can use the same approach? Or they require that binaries are

[jira] [Created] (IGNITE-13354) Add ClusterMetrics to the new framework

Nikolay Izhikov created IGNITE-13354: Summary: Add ClusterMetrics to the new framework Key: IGNITE-13354 URL: https://issues.apache.org/jira/browse/IGNITE-13354 Project: Ignite Issue

Cpp thin client transactions support ready for review.

  Igniters, seems i complete with transactions in thin cpp client implementation [1], part of iep-34 [2]. Can anyone review my decision ? Failed test seems not mine, looks like after fresh master rebase it will gone.   [1]  https://issues.apache.org/jira/browse/IGNITE-13308 [2] 

Re[2]: new connection event

may be jmx would be enough here ?   >Hello! > >Why not the Failure Handler then? > >(I'm only half-joking). > >Regards, > >-- >Ilya Kasnacheev > > >ср, 12 авг. 2020 г. в 09:54, Oleg Ostanin < oleg.alex.osta...@gmail.com >: >  >> Thank you for the response. Yes, we have a simple warning in log,

Re: new connection event

Hello! Why not the Failure Handler then? (I'm only half-joking). Regards, -- Ilya Kasnacheev ср, 12 авг. 2020 г. в 09:54, Oleg Ostanin : > Thank you for the response. Yes, we have a simple warning in log, but in > case SSL error needs an immediate human attention it would be better to set

Re: [DISCUSSION] Add index rebuild time metrics

I seem to be in the minority here :) Fine, let's make it as clear as possible which metric method (localCacheSize) should be called in order to retrieve a 100% progress milestone. I've left comments in the PR. On Tue, Aug 11, 2020 at 4:31 PM Nikolay Izhikov wrote: > > I propose to stick with a

Re: new connection event

Thank you for the response. Yes, we have a simple warning in log, but in case SSL error needs an immediate human attention it would be better to set a listener for such events. вт, 11 авг. 2020 г. в 17:59, Ilya Kasnacheev : > Hello! > > I'm not sure this is a good event. Events are

Re: Apache Ignite 3.0

Hi, Val. > On 12 Aug 2020, at 01:31, Valentin Kulichenko > wrote: > > Hi Petr, > > I agree -- we should better modularize the platform. The current way if very > error-prone, especially during upgrades -- any changes made within > IGNITE_HOME (configs, scripts, modules, etc.) must be merged