| Table of Contents |
|---|
...
User can add node to cluster by adding configuration information in configuration file and running playbook (see deployment manual).
| Warning |
|---|
Please be careful with deployment of database part in playbook. During initial deployment scripts in playbook create clean database structure. If you create playbook for adding node you must exclude database part, otherwise all data will be lost. It is strictly recommended to backup database before any actions with playbooks. |
Remove node
To remove FIXEdge node user must do the following
...
Sessions and schedules properties are managed via Configuration Service with the help of Configuration Tool. All other configuration parameters are managed via local property files similar to standalone FIXEdge (see)
Logs
FIXEdge node logs are collected in centralized storage - Splunk system. You can concern How to integrate FIXEdge with Splunk document.
User must create data source input on tcp port=1514, sourcetype=log4j
...
Deployment of additional instances of services is implemented via playbook similar to adding of FIXEdge nodes. User can run several instances of Configuration Service. All instances are equal (there is no leader), users can use any of them.Consul Coordinator allows several instances of service running.
Removing of services can be done in the same way as for FIXEdge nodes.
Configuration service
Configuration Files
...
/srv/configuration-service
Logs
directory path for logs:
/srv/configuration-service/logs
...
User can add, modify and remove sessions with Configuration Tool.
Schedule management
User can add, modify and remove schedules with Configuration Tool.
Troubleshooting
Check health state of services and nodes
...