Thanks Evgenii
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Veena,
There is a message in the logs:
[WARNING][jvm-pause-detector-worker][IgniteKernal] Possible too long JVM
pause: 8023 milliseconds.
In most cases, it is a sign of the long GC pause. Of course, this JVM pause
can be related to the problems with a virtual environment or something
else,
Hi Ilya,
How can a node reachability resolver or Tcp Segmentation resolver help in
discovering segmentation due to GC pauses ? What is the best way to discover
segmentation on a node due to GC pauses ?
regards,
Veena
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
eper
>>> Discovery which was created specifically to support large clusters.
>>>
>>> Stan
>>>
>>> On Mon, Dec 9, 2019 at 4:02 PM Prasad Bhalerao <
>>> prasadbhalerao1...@gmail.com> wrote:
>>>
>>>>
>>>> Can someone please adv
er
>> Discovery which was created specifically to support large clusters.
>>
>> Stan
>>
>> On Mon, Dec 9, 2019 at 4:02 PM Prasad Bhalerao <
>> prasadbhalerao1...@gmail.com> wrote:
>>
>>>
>>> Can someone please advise on this?
>>>
Bhalerao
>> Date: Fri, Nov 29, 2019 at 7:53 AM
>> Subject: Re: Local node terminated after segmentation
>> To:
>>
>>
>> I had checked the resource you mentioned, but I was confused with
>> grid-gain doc describing it as protection against split-brain. Be
> Can someone please advise on this?
>
> -- Forwarded message -
> From: Prasad Bhalerao
> Date: Fri, Nov 29, 2019 at 7:53 AM
> Subject: Re: Local node terminated after segmentation
> To:
>
>
> I had checked the resource you mentioned, but I was
Can someone please advise on this?
-- Forwarded message -
From: Prasad Bhalerao
Date: Fri, Nov 29, 2019 at 7:53 AM
Subject: Re: Local node terminated after segmentation
To:
I had checked the resource you mentioned, but I was confused with grid-gain
doc describing
I had checked the resource you mentioned, but I was confused with grid-gain
doc describing it as protection against split-brain. Because if the node
is segmented the only thing one can do is stop/restart/noop.
I was just wondering how it provides protection against split-brain.
Now I think by
Hello,
Basically this is a mechanism to implement custom logical/network
split-brain protection. Segmentation resolvers allow you to implement a way
to determine if node has to be segmented/stopped/etc in method
isValidSegment() and possibly use different combinations of resolvers within
Hi,
Can someone please help me out with following questions.
1) If the ignite is capable of detecting nodes segmentation and taking
STOP,RESTART_JVM or NOOP action based on configured failure handlers then
why do we need explicit SegmentationResolvers?
2) Does ignite always treat node
Hello,
Please refer to documentation on failure handler:
https://apacheignite.readme.io/docs/critical-failures-handling.
As it is correctly stated, we cannot restart the JVM without external
tooling, by default we are doing this for nodes that were started with
ignite.sh/bat so that Ignite start
Why did you have to extend stop handler?
Why couldn't you use the existing one provided in ignite?
Btw the question is about how to restart the JVM? JVM can't restart itself
without taking outside tool/scripts help.
Thanks,
Prasad
On Wed 27 Nov, 2019, 9:43 PM Surinder Mehra You can extend the
You can extend the stopnode handler and stop Java process when
stopnodehandler is called by ignite.
We did similar thing in our project
On Wed, Nov 27, 2019, 17:00 Akash Shinde wrote:
> Hi ,
>
> I have started four server nodes. One of the node got terminated
> unexpectedly giving following
14 matches
Mail list logo
