Yeah the aggregate auto-balance is something we looked at, and may fool with.   In this case I'm also particularly interesting in just knowing when an aggregate is getting full.

We likely will end up using OCUM a bit more extensively, since all these alerts are more configurable there, vs. in the filers themselves.


On Wed, Jun 13, 2018 at 7:54 AM, Sebastian Goetze <spgoetze@gmail.com> wrote:

You guys are aware of the Aggregate Auto Balance functionality?

It seems, that it would do automatically, what you did manually...:

autobalance aggregate config modify

autobalance aggregate show-aggregate-state

autobalance aggregate show-unbalanced-volume-state

cluster1::*> autobalance aggregate show-unbalanced-volume-state -instance
Node Name: cluster-1-01
DSID of the Last Volume Queried: 1025
Aggregate: aggr_1
Name of the Volume: ro10
Last Time Threshold Crossed: 3/12/2014 16:20:18
Last Time Volume Was Moved: 3/11/2014 10:16:04
Is Volume Currently Moving: false
Is Volume Quiesced: false
Total Size of the Volume: 20.20MB
Volume's Attributes: Over IOPS Threshold
Stabilizing
Last Time Volume State Was Checked: 3/13/2014 08:20:18
Node Name: cluster-1-01
DSID of the Last Volume Queried: 1026
Aggregate: aggr_1
Name of the Volume: test
Last Time Threshold Crossed: 3/12/2014 16:20:18
Last Time Volume Was Moved: 3/11/2014 10:16:42
Is Volume Currently Moving: false
Is Volume Quiesced: false
Total Size of the Volume: 20.20MB
Volume's Attributes: Over IOPS Threshold
In Mirror
Stabilizing
Last Time Volume State Was Checked: 3/13/2014 08:20:18

At the diagnostic level, there are additional modifiable parameters.
cluster1::*> autobalance aggregate config show
Is the Auto Balance Aggregate Feature Enabled: false
Mode of the Auto Balance Aggregate Feature: recommend
Polling Interval: 3600
Threshold When Aggregate Is Considered Unbalanced (%): 70
Threshold When Aggregate Is Considered Balanced (%): 40
Volume Operations Threshold (IOPS): 100
Volume Operations Threshold Not Exceeded for Duration: 24
Volume Not Moved Again for Duration: 48

And on the volume:

volume modify
Modify volume attributes...

[ -is-autobalance-eligible {true|false} ] - Is Eligible for Auto Balance Aggregate (privilege: advanced)
If the Auto Balance feature is enabled, this parameter specifies whether the volume might be considered for
system workload balancing. When set to true , the Auto Balance Aggregate feature might recommend moving
this volume to another aggregate. The default value is true .

Just a suggestion...


Sebastian



On 18/06/09 4:41 PM, John Stoffel wrote:
Mike> In Ontap 8, we used to route this message to a group of
Mike> operators, who would move volumes around when aggregates started
Mike> getting full.

I assume you got this message from trolling the message log?  

Mike> I don't see the associated message in the Ontap 9 message
Mike> catalog, or anything that looks similar.  

I'd probably just script something out that does a show aggr and then
parses the numbers and alerts on them.  'dashboard storage show' might
also be something to look at, but much harder to parse and work with.

Do you run with a bunch of small aggregates, or much fewer, larger
aggregates?  I personally like monster aggregates, so I don't have to
move volumes very often if at all.

But I do have some smaller dedicated aggregates for some Oracle DBs
which need the dedicated IOPs.  This is still on a 7-mode 8.x system
which is running out of steam...

John

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters