...
If the admin node is unavailable, it will not be possible to deploy software updates, join additional nodes to the cluster, and some periodic scheduled tasks will not run, but there is no impact on availability. This node should be restored before attempts to modify the configuration are made - contact support for assistance in reinstating this node if it is totally lost.
FAQs
Q: Is it possible to use a read replica database?
A: Provided replication lag is consistently less than 5s, it is possible to use a read-replica for searching. Typically, however, this is not a useful configuration as the replica also needs to have a standby to maintain HA, so it is usually preferable to simply deploy a more powerful instance type for the writable database. It is not possible at the present time to provide a list of database instances to achieve HA with multiple independent read replicas. If you would like to pursue this option, please discuss the specifics of your requirements with us.
Q: Is Amazon Aurora supported?
A: No. Amazon Aurora, in MySQL compatible edition, still has important behaviour differences which cause issues with non-unique UUIDs.
Q: Can S3 be used instead of EFS?
A: No. Chorus requires a block-level filesystem, so S3 isn't currently supported. It is technically possible to mount S3 as a virtual filesystem (s3fs), but this is not recommended - the filesystem compatibility layer adds significant performance penalties, and it can generate large numbers of S3 requests.
