Currently, when starting oracle, it checks fast if it can connecto to EC/CC RPC API endpoints. If any error occurs, oracle shuts down. This is a problem when executing a "docker-compose up" for the first time when EC/CC do not have a database initialized, since they take some time initializing their configuration and API. Oracle service already has a "depends-on" of EC/CC services, but this is not enough at the moment
It could be useful to make oracle wait for EC/CC API's to be ready before trying to connect to their endpoints, so that the oracle operator doesn't have to restart the oracle container.
This problem could be solved by:
- Making oracle service wait a little bit before initializing ("depends-on" is not enough).
- Change oracle code, making it wait some seconds before checking EC/CC APIs.
Currently, when starting oracle, it checks fast if it can connecto to EC/CC RPC API endpoints. If any error occurs, oracle shuts down. This is a problem when executing a "docker-compose up" for the first time when EC/CC do not have a database initialized, since they take some time initializing their configuration and API. Oracle service already has a "depends-on" of EC/CC services, but this is not enough at the moment
It could be useful to make oracle wait for EC/CC API's to be ready before trying to connect to their endpoints, so that the oracle operator doesn't have to restart the oracle container.
This problem could be solved by: