Of course I meant ticket [1] increased cluster stability in situation of
blinking network.
[1] https://issues.apache.org/jira/browse/IGNITE-7163
On Mon, Jun 8, 2020 at 1:51 PM Sergey Chugunov
wrote:
> Vladimir,
>
> Adding to what Alexey has said I remember that cases of short-term network
> iss
Vladimir,
Adding to what Alexey has said I remember that cases of short-term network
issues (blinking network) were also a driver for this improvement. They are
indeed hard to reproduce but have been seen in real world set-ups and have
proven to increase cluster stability.
On Sat, Jun 6, 2020 at
Vladimir,
Such behavior can be introduced by an erroneous firewall configuration (I
can't find a link, but I remember that quite a large number of major
incidents are caused by an incorrect configuration change). If such a case
can be detected, we prefer Ignite to shutdown some of the nodes rather
Finally, I got your question.
Back in 2017-2018, there was a Discovery SPI's stabilization activity. The
networking component could fail in various hard-to-reproduce scenarios
affecting cluster availability and consistency. That ticket reminds me of
those notorious issues that would fire once a we
Denis,
I have no nodes that I'm unable to interconnect. This case is simulated
in IgniteDiscoveryMassiveNodeFailTest.testMassiveFailSelfKill()
Introduced in [1].
I’m asking if it is real or supposed problem. Where it was met? Which
network configuration/issues could be?
[1] https://issues.
Vladimir,
I'm suggesting to share the log files from the nodes that are unable to
interconnect so that the community can check them for potential issues.
Instead of sharing the logs from all the 5 nodes, try to start a two-nodes
cluster with the nodes that fail to discover each other and attach th
Denis, hi.
Sorry, I didn’t catch your idea. Are you saying this can happen and
suggest experiment? I’m not descripting a probable case. It is already
done in [1]. I’m asking is it real, where it was met.
04.06.2020 23:33, Denis Magda пишет:
Vladimir,
Please do the following experiment.
Vladimir,
Please do the following experiment. Start a 2-nodes cluster booting node 3
and, for instance, node 5. Those won't be able to interconnect according to
your description. Attach the log files from both nodes for analysis. This
should be a networking issue.
-
Denis
On Thu, Jun 4, 2020 at
Hi, Igniters.
I wanted to ask how one node may not be able to connect to another
whereas rest of the cluster can. This got covered in [1]. In short: node
3 can't connect to nodes 4 and 5 but can to 1. At the same time, node 2
can connect to 4. Questions:
1) Is it real case? Where th
