Re: Apache Ignite 3.0

Folks, Since we all want 3.0 to be a "cleanup" release, I've added a section that lists potential API removals: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0#ApacheIgnite3.0-Removals Please take a look and let me know if there are any objections, or if there is anything tha

Re: Apache Ignite 3.0

Hi Ilya, Can you please describe your vision of how it should work? Let's say, I want to set up a cluster of several standalone server nodes with a couple of optional modules enabled. What are my steps? -Val On Thu, Aug 13, 2020 at 6:03 AM Carbone, Adam wrote: > Good Morning from the EastCoas

[Apache Ignite Virtual Meetup] Building a Blockchain Network with Apache Ignite

Hello Igniters, I would like to share with you the video recording[1] of our presentation from the last Ignite Virtual Meetup. Although our use case might sound a bit extraordinary, we are extremely satisfied with our decision to use Ignite for it. Thanks, Branimir [1] https://youtu.be/lCiZ3x8IRv

[jira] [Created] (IGNITE-13360) .NET: Add Timeout to Thin Client services

Pavel Tupitsyn created IGNITE-13360: --- Summary: .NET: Add Timeout to Thin Client services Key: IGNITE-13360 URL: https://issues.apache.org/jira/browse/IGNITE-13360 Project: Ignite Issue Type

[jira] [Created] (IGNITE-13359) .NET: Add GetServiceDescriptors to Thin Client Services

Pavel Tupitsyn created IGNITE-13359: --- Summary: .NET: Add GetServiceDescriptors to Thin Client Services Key: IGNITE-13359 URL: https://issues.apache.org/jira/browse/IGNITE-13359 Project: Ignite

Re: Thin Client Kubernetes discovery

Max, There is no point in using DNS names instead of IP addresses if an application developer stills needs to set the latter in a thin client configuration. The developer should just pass a single parameter, start the client and forget about the connectivity matters. The state of the cluster will

Re: Apache Ignite 3.0

Good Morning from the EastCoast I have to agree that the larger industry is tending towards immutability, and that you build once and test, then you promote/migrate that immutable binary object, be is a library or a docker image etc... however there are still patterns that allow you to determi

Re: Apache Ignite 3.0

Hello! On the contrary, I would suggest that apache2 way was outdated even at times when apache was all rage. Now the nginx approach is prevalent: on devops phase, assemble a custom bundle with all plugins included, store it somewhere, and ship it to production as a whole to remove any on-the-fly

[jira] [Created] (IGNITE-13358) Improvements for partition clearing related parts

Alexey Scherbakov created IGNITE-13358: -- Summary: Improvements for partition clearing related parts Key: IGNITE-13358 URL: https://issues.apache.org/jira/browse/IGNITE-13358 Project: Ignite

Re: [DISCUSS] Best way to re-encrypt existing data (TDE cache key rotation).

Hello all. I'm working on TDE cache group key rotation [1] and I have a couple of questions about partition re-encryption. As described in the wiki [2], the process of re-encryption at the moment consists of sequentially marking memory pages as dirty, this process looks not resource-intensive. Do

Re: Thin Client Kubernetes discovery

Hi, StatefulSet provides predictable naming, then it should be easy to configure a client with addresses ignite-1,ignite-2...ignite-N. So there is no need in custom discovery, IPs etc. I think it corresponds to k8s patterns, as some pods are different from others as they store specific partitions (

Re: Thin Client Kubernetes discovery

Vladimir, I agree with you, StatefulSet is not related here. > it's not a strict rule to communicate only directly with a pod > running a node with a primary partition Yes, if a node with a primary partition is not known or can't be contacted, we fail over to a default (random) node (afaik this i

Re: Thin Client Kubernetes discovery

Hi guys, Maybe I'm missing something but I don't undestand how StatefulSet relates to the described functionality. StatefulSet is more about persistence. Correct me if I'm wrong but my current understanding is that we don't need to have any explicit state for a thin client connection. I'd like thi

[jira] [Created] (IGNITE-13357) .NET: Add includeExpired to ContinuousQuery

Pavel Tupitsyn created IGNITE-13357: --- Summary: .NET: Add includeExpired to ContinuousQuery Key: IGNITE-13357 URL: https://issues.apache.org/jira/browse/IGNITE-13357 Project: Ignite Issue Ty

[jira] [Created] (IGNITE-13356) Documentation Change needed: PluginProvider loading changed from 2.8.1

Veena Mithare created IGNITE-13356: -- Summary: Documentation Change needed: PluginProvider loading changed from 2.8.1 Key: IGNITE-13356 URL: https://issues.apache.org/jira/browse/IGNITE-13356 Project:

Re: Thin Client Kubernetes discovery

Max, The point of Thin Client k8s discovery feature is to make k8s deployment simple - similar to KubernetesIPFinder for thick clients and servers. - I don't think that enabling partition awareness is related to a StatefulSet in any way - Not everyone is able to / wants to define a StatefulSet -

Re: Thin Client Kubernetes discovery

In case of an enabled partition-awareness feature or sessions I suppose that a state appears. And as we have a state we should use the stateful deployment of kubernetes with StatefulSet [1]. In that case addresses of nodes are predictable and aren't changed so one can configure a client with them.

Re: Thin Client Kubernetes discovery

Max, Denis, Partition Awareness [1] is our main reason to have a specialized k8s discovery mechanism in Thin Clients. k8s ingress mechanism is fine for a single client connection, but in Partition Aware mode thin clients need to connect to every server node, and track nodes as they enter or leave

[jira] [Created] (IGNITE-13355) Now .net does not have RemoteListen,now how to is used to achieve this function?

杨鹏 created IGNITE-13355: --- Summary: Now .net does not have RemoteListen,now how to is used to achieve this function? Key: IGNITE-13355 URL: https://issues.apache.org/jira/browse/IGNITE-13355 Project: Ignite

Re: Thin Client Kubernetes discovery

We're discussing the case when the thin client and server nodes are a part of a single Kubernetes cluster. Ignite thick client uses KubernetesIPFinder to auto-discover other Ignite pods. The IP finder gets IP addresses of other Ignite pods

Re: Apache Ignite 3.0

RPM/DEB will be easy to refactor that way —internal dependency management will help with that. We can start with simple task — divide package into at least the following modules: — apache-ignite: slim package with only necessary runtime libs and scripts (just like slim binary) — apache-ignite