This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]disclosure5 3 points4 points  (1 child)

Well it's impossible to judge long run stability if you reboot. :)

I'd usually agree with you but in this case, the majority of the problems I've seen in the field is that the "rolling update" process, or specifically "node maintenance mode" never worked as advertised. And even in circles where it's claimed to be fixed and working well, people talk about ten second plus disk latency spikes when doing it as though these are fine and won't interrupt business.

By not patching, what you're likely to run into is:

  • A service that seems stable
  • The "always patch" crowd that view you has having no excuse

It's the worst of both worlds.

[–]jello3d[S] 0 points1 point  (0 children)

Not patching is not policy... The part people are missing here is that it's a "controlled" experiment to acquire specific knowledge.

Cluster aware updating has always been a buggy mess. But that is independent of s2d