# Ordinary access to read the database.  Pick one at random.  They all should be about the same.
database_RO=ti-test-use1-maindbro-01.ti.local

# Master database.  Notice the trick we use for alerts_master_info and top_list_master_info.  Those refer to aliases we created in /etc/hosts.  You can change /etc/hosts to point to a different machine.  We might want a similar trick here.  Of course, changing the master database is huge and doesn't happen often.
database_RW=ti-test-use1-maindb-01.ti.local

# This is used by history and the oddsmaker.  This list should be exactly the same on every computer.  The idea is to try to maximize cache use on these databases.  If each client sends similar requests to each server, then the server can respond faster than if each server had to handle every type of request.
history_databases=ti-test-use1-historydb-01.ti.local

history_databases_no_realtime=ti-test-use1-norealtimedb-01.ti.local

# Back office.  If you are worried about breaking the cache, do it on this
# machine.  If you are working with a lot of user data, there's a good chance
# it's already in this machine's cache.
database_back_office=ti-test-use1-maindb-01.ti.local

# Candles.
#database_candles=ti-test-use1-barsdb-01.ti.local
database_candles=ti-test-use1-maindb-01.ti.local:3306:bars

# Paper database
database_paper_master=ti-test-use1-paperdb-01.ti.local:3306:mydb

alerts_multicast_addr=239.200.1.0:2000
top_list_multicast_addr=239.200.2.0:2001
multicast_receiver_fill_in_after=7000

# Kafka Nxcore data
kafka_boostrap_servers=b-1.msk-dev-md-kafka01.7i0n81.c19.kafka.us-east-1.amazonaws.com:9092,b-2.msk-dev-md-kafka01.7i0n81.c19.kafka.us-east-1.amazonaws.com:9092,b-3.msk-dev-md-kafka01.7i0n81.c19.kafka.us-east-1.amazonaws.com:9092

# AlertConfig.json
alert_config_json=/ti/AlertConfig.json