Skip to main content
NetApp Knowledge Base

Why is the FlexGroup size so large after creating an S3 bucket?

Views:
623
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9.8+
  • FlexGroup
  • S3 Bucket

Answer

In ONTAP, the underlying architecture for a bucket is a FlexGroup volume—a single namespace that is made up of multiple constituent member volumes but is managed as a single volume.

In 9.7, a S3 bucket was associated with a FlexGroup. Hence whenever a bucket was created, a new Flexgroup was created underneath, which was the same size as that of the bucket size. The bucket could be created either by specifying aggr-list during bucket create command (in which case those aggregates are picked for provisioning of FlexGroup) or by using auto-provision.
 
From 9.8 onwards, a bucket is associated with a Qtree, enabling us to have multiple buckets on a FlexGroup. The idea here is to have a large size FlexGroup on which multiple buckets can be placed, and the provisioning of FlexGroup is done through Balanced Placement.
 
When the first bucket is created, a large size FlexGroup gets created. After this, when the following buckets are created, they can either be placed on an existing FlexGroup (if they meet the criteria) or they would be placed on a new FlexGroup that would be created as a part of bucket creation. Several criteria are considered while deciding whether to place the bucket on an existing Flexgroup or create a new FlexGroup.

Additional Information

S3 in ONTAP best practices

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.

 

  • Was this article helpful?