Ignite handles SIGTERM and stops the node.
Use IIgnite.Stopped [1] to shut down the app gracefully.
Example: run this program and use "kill" on it - "Stopped." is printed and
the process exits with code 0.
var ignite = Ignition.Start();
ignite.Stopped += (_, _) =>
{
If you have an Apache Ignite deployment on Kubernetes with Linux containers
using the DotNet C# Ignite client, how do you trigger graceful shutdown of
the node?
Kubernetes emits a SIGTERM signal to the pod when it wants to remove it.
That signal is relayed to the process running in the pod
The most straightforward answer might just be to create views in
your source database. Out of the box, the cache store is really designed
for a 1:1 mapping between table and cache. You *can* do more complex
mappings, but it may require coding.
On Wed, 6 Sept 2023 at 09:46, Bram Biesbrouck <
A good place to start would be the monitoring section of the documentation:
https://ignite.apache.org/docs/latest/monitoring-metrics/intro
You can use JMX, OpenCensus, some of the system views; deploying on
Kubernetes doesn't change any of that.
Control.sh, as you suggest, can be used for *ad
Hi all,
I've been experimenting with Ignite over the past months and took an
unexpected (pleasant) deep dive.
Right now, I'm fiddling around with write-through and read-through, but I'm
stuck on one feature I'd really want to find a solution for database table
discriminator values and mapping
Hi,
We have a cluster running on Apache Ignite 2.15 version on Kubernetes.
Could you please advise how to obtain basic cache and cluster nodes
statistics using control.sh script? Ignite Visor is no longer an option (it
used to be sufficient for basic insights).
I've raised
