This site is not optimized for Internet Explorer 9 and lower. Please choose another browser or upgrade your existing browser in order get the best experience of this website.

GraphGrid GDS Operational Guidelines

Last Updated: May 4, 2018

GraphGrid GDS Basic Operational Guidelines

The following are basic operational guidelines that everyone should follow when working with GraphGrid GDS. Note that the GraphGrid GDS Service Level Agreement requires that you follow these guidelines:

·       Monitor your memory, CPU, and storage usage using GraphGrid Metrics.

·       Scale up your instance when you are approaching compute, memory or capacity limits. You should have some buffer in storage and memory to accommodate unforeseen increases in demand from your applications.

·       Enable automatic backups.

·       If your database workload requires more I/O than you have provisioned, recovery after a failover or database failure will be slow. To increase the I/O capacity of an instance, do any or all of the following:

o   Convert from General Purpose to Provisioned IOPS storage, depending on how much of an increase you need.

If you convert to Provisioned IOPS storage, make sure you also use an instance class that is optimized for Provisioned IOPS.

o   If you are already using Provisioned IOPS storage, provision additional throughput capacity.

·       If your client application is caching the Domain Name Service (DNS) data of your instances, set a time-to-live (TTL) value of less than 30 seconds. Because the underlying IP address of an instance can change after a failover, caching the DNS data for an extended time can lead to connection failures if your application tries to connect to an IP address that no longer is in service.

·       Test failover for your instance to understand how long the process takes for your use case and to ensure that the application that accesses your instance can automatically connect to the new instance after failover.