...
A full description of the fields within "infinit.e.properties.configuration" is provided here, but the EC2-specific automated configuration makes populating it considerably easier than in the general case. The remainder of this section describes the EC2-specific configuration.
...
Step 3: Start a load balancer
| Info |
|---|
We've recently found out that the Amazon Elastic Load Balancer has a Balancers have non-configurable timeout of timeouts (eg 60 seconds). This causes can cause problems to some of the Infinit.e operations, such as testing and deleting sources and documents. As a result, we now only use the load balancer to provide automated health-checking of the API, and we use Amazon'You can request Amazon to increase the timeout on their EC2 forums, and they will normally do it within a day or 2. Example forum post I made. An alternative is to use the load balancer only to provide automated health-checking of the API, eg and to use Amazon's DNS service, Route 53, for round-robin load balancing (delegating the "rr" subdomain of ikanow.com: useful link). |
...
First start the 1/3/5 config servers. There are specific templates for a single or three-node configurations (the 5-node case is an easy tweak to the existing template, if needed). The config server parameters are the same as DB but without the unnecessary ReplicaSetIds, IsConfigServer, IsStorageNodeexisting template, if needed). The config server parameters are the same as DB but without the unnecessary ReplicaSetIds, IsConfigServer, IsStorageNode.
The config server Cloudformation template also creates a DNS entry in Route53 for a user-specified Hosted Zone. This is necessary because of a bug in MongoDB where changing the hostname of a config server (eg because the EC2 instance becomes unstable so a new node must be created) requires a complete cluster restart (in order: shutdown API nodes, DB nodes, config nodes; startup config nodes, DB nodes, API nodes). The DNS entry is written into the EC2 metadata in the "DnsName" field.
The only other differences is that InstanceType is one of "t1.micro" or "m1.large". The micro instance should be fine in most cases (and is >10x cheaper).
...
- IsConfigSvr should always be "0", otherwise system-wide problems will occur.
- DnsName should be present, unique, and point via CNAME to the actual hostname, otherwise system-wide issues may occur
Step 5: Start API nodes
The API nodes can then be started. It is difficult to provision in advance the number of nodes because it heavily depends on usage patterns and sort of documents being indexed. It is therefore recommended to start with 2 and add new ones if response times are too long.
...