a9s Redis Resources Considerations
This document describes concerns and limitations to be considered when allocating resources for your a9s Redis plans.
It is possible to configure an a9s Redis service instance with RDB persistency enabled, which means that the Redis data on memory is written to the persistent disk.
Saving the content to the persistent storage is the approach used when backing up an a9s Redis
service instance, and for this reason, your persistent disk size must be higher than your memory
size. Keep in mind that
a9s-parachute will stop the processes when persistent disk usage reaches
a9s Redis configures the maximum amount of memory Redis can use on a service instance, leaving a reserved amount for side processes (a9s Logstash, a9s Consul, a9s Backup Agent, and the OS).
maxmemory is configured as follows:
system_reserved_memory = min[10% of memory, 2GB] total_reserverd_memory = system_reserved_memory + 256MB for the consul agent + 256MB for the a9s Backup Agent + 512MB for a9s Logstash maxmemory = total_memory - total_reserverd_memory maxmemory = max[150MB, maxmemory]
The sentinel port is currently exposed in the service binding. The Sentinel port is currently hardcoded to 6357 + 20000. The templates in template-uploader-errand do not set the port based on the SPI value.