Hi all,
There is the run.sh script that’s required for docker images deployment and
internally it just invokes the default ignite.sh script prior to starting a
node.
So far, so good, but we discovered that it doesn’t propagate system signals
to the JVM due to its internal logic and also lacks
Hi guys,
Alex,
Currently, we are working on the Apache Ignite Kubernetes Operator that
should help with packaging, deploying, and managing the application in the
k8s world. And it turned out that current docker images are not suitable
for running in k8s, cause they won't propagate the signals to
Hi,
I'm working on adding the NodeFilter functionality to the .NET client
https://issues.apache.org/jira/browse/IGNITE-2890
And there are several points I want to highlight regarding the current
implementation:
1) A node filter is being called on every put which seems redundant. This
might be ok
Hello!
I just noticed that the Java thin client throws the following internal
exceptions:
ClientProtocolError
ClientError
Since the classes are not public, there is no way to catch them properly in
user code.
Consider the recent changes, introduced by IGNITE-9410:
throw new ClientProtoc
Pavel,
I think it’s ok to add a new flag.
Though we may change a name to something like #usePlatformCacheIfAvailable
But it may vary depending on the implementation, i.e.
should we throw an error if there is no native cache
available for a platform or just ignore the configuration.
вт, 18
*Subject: *Re: Thin client: compute support
> After all, we don't cancel request
We do cancel a request to perform a task. We may and should use this to
cancel any other request in future.
> Client uses some cluster group filtration (for example forServers()
cluster group)
Ple
Alex,
I think you can create a new IEP page and I will fill it with the Cluster
API details.
In short, I’ve introduced several new codes:
Cluster API is pretty straightforward:
OP_CLUSTER_IS_ACTIVE = 5000
OP_CLUSTER_CHANGE_STATE = 5001
OP_CLUSTER_CHANGE_WAL_STATE = 5002
OP_CLUSTER_GE
Folks,
I started to implement the ClusterGroup API.
There are two tickets at the moment:
- .NET thin client: introduce Cluster API [1]
- .NET Thin Client: introduce ClusterGroup API [2]
The first one introduces the cluster API and is merged to master.
The second ticket is in progress an
