4 ms·
couldn't explain = didn't want to :) But anyway, it also shows that the failover was not properly tested.
by seppel 6y ago
couldn't explain = didn't want to :)
But anyway, it also shows that the failover was not properly tested.
- rightbyte 6y agoOr that the fault killing the first on also killed the failover? Like a rampage JIS encoding control character running over the wires.
- marcan_42 6y agoIt was a memory error. Hardware failure. The failover process is what went majorly wrong here. It seems they had a press conference with more details in Japanese.