sour pier
We have a large customer ingesting data into our Grid and we'd like to limit the amount of bandwidth used.
We're using a DNS round-robin end-point that translates to the storage node client interfaces. And S3 services are connecting straight into port 18082 of the storage nodes.
But when we apply a classification policy on the tenant, and limit aggregate bandwidth, it does not affect amount of datat coming in per second. We're currently on version 11.9.0.3
lean trench
afaik, the bandwidth classification is a limitation one sets on SG loadbalancer endpoints.
sour pier
ah ok.
We've seen it work on a bucket level as well.
But it's a bit strange then that tenant is an option when creating the policy.
Do you know of the documentation where this is explained?
lean trench
you can bind a tenant to a specific endpoint on the loadbalancers. It's a security/provider function. It's been a while since I read the docs
sour pier
My colleague found the documentation that states exactly what you said.
The whole TC function is bound to the LB end-points. So we'll have the function when we get to having the Gateway nodes
lean trench
running without loadbalancers is kind of messy to start with. You don't really get much of the functionality and really no redundancy. Setting up HA-proxy on a couple of VM's isn't a very complicated issue. I've not used the SG software gateway nodes for much of anything serious, but they would also probably even be easier to setup if you have some capacity in your server virutualization infrastructure.
edgy geyser
Traffic classification policies only work with the StorageGRID integrated load balancer endpoints.
https://docs.netapp.com/us-en/storagegrid/admin/managing-traffic-classification-policies.html
I will note that if you were using the integrated load balancers the traffic classification policies are a per load balancer setting and if clients use more than 1 load balancer they would be capable of that limit on each load balancer.
Since you are going direct to the storage nodes, there is no way within the product to limit the client bandwidth.
