Hi Julie!
>> Where did you read this?
Pure logic:
1. 3 nodes cluster is a problematic from point of view of HA (cluster in critical state when node down)
2. Data isn't segmented when one node down in cluster of 3 nodes, only replicated. So you loosing a lot in MPP and it means performance.
Remove node from cluster
Moderator: NorbertKrupa
Re: Remove node from cluster
Thanks, sKwa. So if one node goes down the database is in a critical state because if another node goes down the cluster will fail, right? So I should add another node when we get the $$$
Thanks,
Juliette
Juliette
Re: Remove node from cluster
Hi!
>> So if one node goes down the database is in a critical state because if another node goes down the cluster will fail, right?
Exactly.
To get a full advantage from HA its better to have 4 nodes.
FIX: (one fail in my "pure logic" )
What happens in two nodes?
If data segmented + K-Safety1 so each segment have to be on both nodes, but it's nothing else as a replication!
So you can't have data and segmented and KSafety 1 ==> KSafety = 0 ==> one more node down and good bay database!
And i believe it's a lot of a manual work to remove a node in cluster 3 nodes. Its change all schema.
PS
All this - "IMHO", Im not expert Wait for Sharon - she knows everything
>> So if one node goes down the database is in a critical state because if another node goes down the cluster will fail, right?
Exactly.
To get a full advantage from HA its better to have 4 nodes.
FIX: (one fail in my "pure logic" )
What happens in two nodes?
If data segmented + K-Safety1 so each segment have to be on both nodes, but it's nothing else as a replication!
So you can't have data and segmented and KSafety 1 ==> KSafety = 0 ==> one more node down and good bay database!
And i believe it's a lot of a manual work to remove a node in cluster 3 nodes. Its change all schema.
PS
All this - "IMHO", Im not expert Wait for Sharon - she knows everything