Datagroup access during a datagroup update

Thanks for the suggestions guys.

 

 

Initially we were testing with iControl and saw HTTP request failures during the update. This might have been due to resource starvation during the config change. I believe there were also issues with lookups returning no results for entries that should have been in the class. To simplify the testing, we tried clicking save on the datagroup in the GUI and not using iControl. I didn't retest the iControl update to see if the class size changed. I'll give that a try tomorrow.

 

 

For the customer's project, we'll be using name value pairs in a string datagroup. For the basic load testing, we were just using a name only string datagroup. I'm not sure what the customer will do in terms of updates to the source data. I assume only a small portion of the datagroup name/values will change. So it would be ideal to add/modify/remove only new/changed/stale entries. Our developer said iControl supports these changes in 10.2. So hopefully the class size changing issue will be mitigated. It will be interesting to see whether the load during the changes decreases. I'll post an update after we test more tomorrow.

 

 

I'd still like to get an idea of the expected results for updating a small and/or large datagroup via the GUI. A majority of iRules I've written for customers reference datagroups and it would be a significant change in administration for customers if they needed to limit datagroup updates to maintenance windows. Should the datagroup contents be removed incrementally and then be restored incrementally? If so, is this considered a defect? Has the behavior changed over recent versions?

 

 

Thanks, Aaron