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 ident
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
I agree, but there is a core element here that might be worth considering
for IA, which is the ability to flag a node as [temporarily] unhealthy or
unavailable so application logic can use that as a part of the IA toolset.
Just a thought... :)
Thanks,.
Raymond.
On Fri, Feb 19, 2021 at 2:05 AM Ily
Hello!
This sounds like a too detailed and peculiar scenario that should be taken
care of on the application level, as you already do.
Regards,
--
Ilya Kasnacheev
ср, 17 февр. 2021 г. в 23:50, Raymond Wilson :
> I Ilya,
>
> Sorry, that was a response to another problem!
>
> In this case, we h
I Ilya,
Sorry, that was a response to another problem!
In this case, we have a more asynchronous mode of query-response where the
processing node can asynchronously send back a response to a query. The
reasons for this are: (1) Some responses are effectively streams of data
and we can't structure
Hi Ilya,
That is the current method we use to stop the grid.
However, this can leave uncheckpointed changes in the in-memory stores
(only in the WAL), so when we restart the grid it goes into the cache
recovery mode which is very slow.
Raymond.
On Thu, Feb 18, 2021 at 3:34 AM Ilya Kasnacheev
w
Hello!
Why can't you just use Ignite.stop(instanceName, false)?
Just make sure your projections are not singleton and the tasks will be
rolled over.
Regards,
--
Ilya Kasnacheev
вт, 9 февр. 2021 г. в 06:41, Raymond Wilson :
> All,
>
> We have a very similar requirement as described in this it
All,
We have a very similar requirement as described in this item:
https://issues.apache.org/jira/browse/IGNITE-10872
Namely, when removing a node from a Ignite grid, we want to do two things:
1. Prevent new requests from reaching it
2. Allow all running requests the node is involved in to compl
Hello!
This will happen when this file is deleted while the instance is running.
Not sure who deleted it. Maybe you tried to start another node with the
same consistent id in the background?
You should avoid calling setActive() every time since it will lead to data
loss.
Regards,
--
Ilya Kasnac
These are the full set of logs, if it helps-
[10:10:56,860][WARNING][main][G] Ignite work directory is not provided,
automatically resolved to: /home/dsudev/ignite-master/work
[10:10:56,873][WARNING][main][G] Consistent ID is not set, it is recommended
to set consistent ID for production clusters (
We’d need to see more of the exception. It says it couldn’t write a file, but
your snippet doesn’t say why.
> On 7 Jan 2021, at 10:51, rakshita04 wrote:
>
> I am also getting below error on my ignite logs-
> [20:00:50,515][SEVERE][db-checkpoint-thread-#54][] Critical system error
> detected. Wi
I am also getting below error on my ignite logs-
[20:00:50,515][SEVERE][db-checkpoint-thread-#54][] Critical system error
detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=Unmodi
It shouldn’t cause a crash, but since you don’t need to activate an already
active cluster maybe it’s not well tested.
Sending the node a TERM signal (press ^C) is good way to stop a node.
> On 7 Jan 2021, at 09:26, rakshita04 wrote:
>
> can SetActive() cause the crash?
> is this way okay to
can SetActive() cause the crash?
is this way okay to terminate the process by kill or there is some better
way?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Not that it excuses the crash, but why are you calling activate every time the
node starts? It should be called once, the first time all the nodes are
present. The cluster will auto-activate every time after that.
Regards,
Stephen
> On 7 Jan 2021, at 08:56, rakshita04 wrote:
>
> it works, th
it works, the process is stopped but when application is started using the
same Database node, it crashes with below logs on terminal-
Ignite node stopped OK [uptime=00:00:55.197]
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x76c9f208, pid=26716, ti
Issuing a command like "kill process_id" doesn't work?
regards.
On Thu, Jan 7, 2021 at 4:14 PM rakshita04
wrote:
> Hi Team,
>
> We are using apache-ignite for our applications running on 2 machines and
> connected over network.
> We are facing some issue where if kill is performed on running a
Hi Team,
We are using apache-ignite for our applications running on 2 machines and
connected over network.
We are facing some issue where if kill is performed on running application,
it somehow corrupts the node and then node never comes up and keep on
rebooting.
Is there a way to handle this shut
wrote:
> Hello!
>
> Unfortunately there is no graceful shutdown. Maybe consider asking this
> question on developers list?
>
> Regards,
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Hello!
Unfortunately there is no graceful shutdown. Maybe consider asking this
question on developers list?
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi
I would like to continue this conversation
What is the best way to perform a rolling restart of Ignite nodes to
guarantee no data loss?
I think Ignite should be able to stop a node in data-safe fashion: wait
until all data are moved to another nodes and then stop
Can I somehow ask a node to
Hi Sam,
> is there a chance that stop method call would block long time or
> hang depending on what jobs are running?
> Would it be safe to wrap a wait timeout & call stop(null, false) again if
> taking too long?
In the vast majority of use cases, it will not be a problem I think,
because tasks/j
*1. */> if i call this method, Ignition.Shutdown(null, false);
The Ignition class does not contain the `Shutdown` method [1], [2] Perhaps,
you mean 'stop'. /
-> ah, yes stop method in ignite dotnet C# API.
Apache.Ignite.Core.Ignition
bool Stop(string name, bool cancel)
*2. */> Does the sh
Hello Sam,
> if i call this method, Ignition.Shutdown(null, false);
The Ignition class does not contain the `Shutdown` method [1], [2] Perhaps,
you mean 'stop'.
> Does the shutdown method block until all local node data is rebalanced to
> other nodes?
No, it does not. The second parameter of 'sto
Hello,
We are running many ignite server nodes in windows VM scaleset in a cloud.
But sometimes cloud provider forcefully reboot multiple VMs for system
update (even though update policy is set to manual, it forces reboot
sometimes)
Cache mode is partitioned cache with 2 backups.
The worst cas
Hi Jaipal,
All data should be flushed to back store automatically on graceful shutdown.
On Wed, Apr 5, 2017 at 10:44 AM, Jaipal Reddy
wrote:
> Hii,
>
> We are using Apache Ignite for caching and using its writeBehind feature
> for pushing updated data asynchronoulsy to Oracle DB. T
after 512 ache entries are updated or at the end of 60 seconds(
which ever is earlier). Say, I initiate a graceful shutdown (not a server
crash) of the Ignite Instance and I have 10 records which are updated in
cache but are NOT YET updated to DB. During the graceful shutdown, will the
IgniteCacheStore
Thanks, now it waits for task completion. I've also implemented shutdown
check during the tasks to allow correct termination.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Graceful-shutdown-tp4911p5088.html
Sent from the Apache Ignite Users mailing
message in context:
http://apache-ignite-users.70518.x6.nabble.com/Graceful-shutdown-tp4911p4920.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ion
?
Thanks.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Graceful-shutdown-tp4911.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
30 matches
Mail list logo
