We've recently learned that we can make some adjustments (and/or come up with a whole new cluster configuration) to the AWS ElastiCache service within cloud.gov, and there are several things we ought to factor in to make some adjustments.
The most important change we ought to make and request is adjusting the maxmemory-policy to make sure old keys get cleared out when space starts to become an issue. A different cluster mode might also be necessary.
Outside of that, there are several things we need to research:
This is the information cloud.gov had sent us in response to using up all of the memory in our Redis instance previously. Let's go through this information and determine what our next steps ought to be.
We've recently learned that we can make some adjustments (and/or come up with a whole new cluster configuration) to the AWS ElastiCache service within cloud.gov, and there are several things we ought to factor in to make some adjustments.
The most important change we ought to make and request is adjusting the
maxmemory-policyto make sure old keys get cleared out when space starts to become an issue. A different cluster mode might also be necessary.Outside of that, there are several things we need to research:
This is the information cloud.gov had sent us in response to using up all of the memory in our Redis instance previously. Let's go through this information and determine what our next steps ought to be.