There's lots of reasons to update your ZFSSA code. You should all be doing this. Yes, I have heard all of the excuses why people don't. Yes, I know some of you don't like it, or you're busy, or you don't want to take the 15 minutes of stress to fail-over one controller to another when it has to reboot. Sorry, but I can't agree with you. Oracle ZFSSA engineers push out these updates for a REASON. Often that reason is that the 600 PETABYTES of ZFSSA inside our Oracle customer Cloud services saw some kind of bug or issue, and they want to make sure YOU don't hit the same bug.
Also, as in this example, they roll out some very cool and welcome features. Such as the ability we now have to remove a Readzilla or Logzilla disk from a pool! This was much harder to do last year, and now it's a piece of cake (the cake is a lie).
Here's another one. Take a look at my new ARC Ratio section on my Status Dashboard :
I can now see my current ARC (Adaptive Responsive Cache) hit ratio, a very important metric that I love to keep my eye on. We are shooting for 99%, or at least keeping it over 85% for a vast majority of the time. If it falls below 80% for any given length of time, then you don't have enough DRAM for the workloads you are running. Talk to your local storage SE about how to improve this.
You can change the layout of these status charts, and remove ones you don't need, by going to Settings, then Layout.