A two-node ROBO cluster is configured with a witness VM.

What happens when Node A goes down?
33 comments · newest first
IV
Ivette
10 months ago
If Node A goes down, Node B should handle it smoothly.
MO
Mose
11 months ago
Wait, are you sure about that? Sounds too easy.
PH
Phung
11 months ago
Definitely D, that's how it works!
JA
Jacob
11 months ago
I think the cluster stays up, right?
KA
Katy
11 months ago
Node B takes over with the witness VM!
KA
Katheryn
11 months ago
I'm leaning towards option D because it sounds familiar from our study sessions, but I could be mixing it up with another scenario.
HA
Hannah
12 months ago
I feel like I read that Node B would send a request to the Witness VM, but I can't recall if that means it goes into single-node mode or something else.
FA
Fallon
12 months ago
I remember a practice question where the cluster remained operational with just one node, so I think option C could be correct.
JA
Jaime
1 year ago
I think when Node A goes down, Node B might take over, but I'm not sure if it needs to contact the Witness VM or not.
CA
Carma
1 year ago
I think the key here is understanding how the ROBO cluster handles single-node scenarios. I'll need to carefully consider the implications of the witness VM in this setup.
ER
Ernest
1 year ago
Based on the options, it seems like the cluster should be able to maintain operations even with Node A going down. The witness VM should help Node B take over leadership.
TI
Tijuana
1 year ago
I'm a bit confused here. Does the cluster go into read-only mode, or does Node B take over? I'll need to review the ROBO cluster failover behavior.
EZ
Ezekiel
1 year ago
Okay, let's see. With a two-node ROBO cluster and a witness VM, I'm guessing the cluster will try to maintain availability if one node goes down.
MI
Miss
1 year ago
Hmm, this looks like a tricky one. I'll need to think carefully about the cluster configuration and how it responds to node failures.
NA
Nan
1 year ago
Whoa, hold up! Option B sounds like a total shutdown. That can't be right. I'm feeling confident about Option C - let the cluster keep on trucking without any intervention.
AL
Albina
1 year ago
User 3: Yeah, I also think Option C is the best choice for this scenario.
SK
Skye
1 year ago
User 2: I think Option C makes more sense, let the cluster keep running smoothly.
LE
Leanora
1 year ago
User 1: I agree with you, Option B does sound extreme.
MI
Misty
1 year ago
Hmm, I'm leaning towards Option A. Losing a node in a two-node cluster sounds like it would bring the whole thing down. Better play it safe, right?
AR
Arthur
1 year ago
User1: Definitely, it's always better to plan for potential failures in a cluster setup.
JA
Jacob
1 year ago
User2: I agree, it's better to be prepared for the worst-case scenario.
EL
Eleonora
1 year ago
User1: I think you're right, Option A seems like the safest choice.
RO
Rolande
1 year ago
Ha! Witness VMs, I've always thought they were more trouble than they're worth. Anyway, I'm going with Option D. Gotta love that single-node mode!
ST
Stephaine
1 year ago
Definitely, having Node B switch to single-node mode automatically is a great feature.
EM
Emilio
1 year ago
I think Option D is the way to go as well. It's good to have that failover in place.
DA
Davida
1 year ago
Yeah, single-node mode is definitely convenient. No need to worry about the cluster going down.
GW
Gwenn
1 year ago
I agree, Witness VMs can be a hassle. Option D does seem like the best choice.
CA
Carlota
1 year ago
Option C seems plausible, but I'm not entirely convinced. I'd need to double-check the specifics of ROBO cluster failover behavior to be sure.
AM
Amie
1 year ago
User 2: I agree, Node B would send a leadership request to the Witness VM.
JO
Jody
1 year ago
User 1: I think option D is the correct answer.
RO
Rosann
2 years ago
But if Node A goes down, Node B should take over, right?
FR
Frankie
2 years ago
I disagree, I believe it's A.
RO
Rosann
2 years ago
I think the answer is D.