<div dir="ltr">Vladis, I hear ya and agree to that. Problem is I have seen big and by big, I mean biggggggggg infrastructures asking for ksplice since certain sales people of certain company introduced them to the utopia that is called downtime-less-patching-and-upgrading. And obviously, if you have worked with the CLI a bit less than most of us have already had, you get the sweet inclination to go with sales and you know, voila.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 19, 2013 at 2:16 PM, <span dir="ltr"><<a href="mailto:Valdis.Kletnieks@vt.edu" target="_blank">Valdis.Kletnieks@vt.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, 19 Nov 2013 09:48:27 -0500, Soham Chakraborty said:<br>
> I don't really think ksplice has garnered much love from upstream.<br>
<br>
</div>The most common word used upstream to describe ksplice is "bletcherous".<br>
<br>
The reason it's disliked is because it's a poor solution for the problem.<br>
Although ksplice-like technology was used for years to upgrade telco<br>
switches on the fly, that was motivated by two major factors:<br>
<br>
1) Nobody at a telco wants to drop dial tone while a switch reboots.<br>
2) Telco switches are building-sized and expensive, so HA failover wasn't a<br>
realistic option.<br>
<br>
Although the first is still an issue for many sites, there's little or no<br>
justification in 2013 for the second.<br>
<br>
If you're in the sort of environment where you really need the sort of uptime<br>
that drive you to consider ksplice, you *really* should be doing load<br>
balancing and HA failover with heartbeats - that will not only allow you<br>
to actually reboot each server cleanly, but *also* protect you against blown<br>
DIMMs, crashed system disks, and all the *other* whoopsies that can cost<br>
you one or two nine's of reliability.<br>
<br>
Seriously - if you can't afford the downtime to reboot, youy can't afford<br>
*NOT* to be doing a full HA configuration - and possibly looking at<br>
geographic separation of the hot failover site.<br>
</blockquote></div><br></div>