Overview
config/topology.txt is a '|'-separated text file with fixed columns.
| Column | Name | Description |
|---|---|---|
| 1 | Instance Name | Name of the instance (must be unique) |
| 2 | Host Name | The host of the instance |
| 3 | Preset | Reference to one set of pre-defined configuration settings that control memory and port assignments |
| 4 | Indexer Name | Name of the instance that provides the index for this live instance, or '-' if this instance is an indexer |
| 5 | Comments | Additional comments, can be empty |
An example config/topology.txt might look like this:
# # This is a comment. # demo|indexer.example.com|1|-|Indexer and Preview environment for demo setup demolive1|live1.example.com|2|demo|Live Query Server for demo setup demolive2|live2.example.com|2|demo|Live Query Server for demo setup
Presets
The 'preset' column in config/topology.txt is only used by bin/setup-cluster to configure the settings of the new FAS instances based on default setting templates delivered with FAS. Those settings control which ports are used by which application, and how much memory is assigned to each application.
 |
No two default templates refer to the same port, so that for a setup with multiple instances on the same physical machine it is enough to ensure that the 'preset' column value is unique per machine. |
The available 'preset' values can be determined using the deployment-agent REST API, for example using curl:
$ curl http://localhost:8177/installation/FAS/presets 1 2 3 ...
|
Because the names of the configuration setting sets delivered with FAS are simple numbers the 'preset' is also sometimes referred to as 'instance number'. |
The contents of each of those presets can also be shown in a similar manner:
$ curl http://localhost:8177/installation/FAS/preset/1
#1
#Thu Mar 15 13:13:51 CET 2012
qserver_http_port=8180
qserver_memory=1500
searchindexer_memory=900
syncclient_memory=20
syncclient_serverport=${syncserver_serverport}
syncserver_memory=60
...
After bin/setup-cluster has configured the instances, the deployment-agent set-option and get-option commands can be used to further modify the instance configuration.
Comments
0 comments
Please sign in to leave a comment.