On 11/19/14 07:52 AM, Fred Liu via illumos-discuss wrote:
18 ноября 2014 г. 11:20:21 CET, Fred Liu via illumos-discuss
<[email protected]> пишет:
Sorry if it is a duplicated topic.
For illumos-based OSes, patching ZFS means patching kernel. Solaris
used to have this possibility.
Solaris has live patching, but not live activation of kernel patches - a
reboot is required.
Most of the Illumos distros do the same.
Sun did live activation of kernel patches over 10 years ago (Project
DUKS - https://blogs.oracle.com/jimmo/entry/the_fate_of_hot_patching)
but never productized it. The hard part is not the kernel live patching,
but the management infrastructure that records precisely what you are
running, and that was beyond the capabilities of the packaging system in
use back then. Oracle has said they are revisiting this in Solaris, now
that Solaris has a packaging system which can handle it (IPS) and Oracle
have the Ksplice technology in their Linux.
I think it is also the guideline for "zpool|zfs upgrade" command
operation even I played them on-the-fly without any issues. But ZFS is
already a proven *enterprise* storage solution, we should definitely
expect the minimum service outage just like NetApp/EMC.
When you want that level of availability, clustering is normally used,
and ZFS works fine in clusters (at least in Solaris/Illumos - I don't
know about ZoL).
You do not normally issue "zpool|zfs upgrade" commands as part of a
software upgrade, as it would prevent you from rolling back. It's
normally only done after period of stable running (and for a cluster,
after all nodes have been software upgraded), when you are sure you no
will longer need to roll back.
--
Andrew Gabriel
-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com
