Now that we have a health check resource on our operations endpoint (see #928) we can use it to start the docker compose network in the example in a correct way.
lets add to each service a healthcheck, and explicitly encode the arma server dependencies with depends_on.
See:
https://github.com/hyperledger/fabric-x-evm/blob/main/compose.fabric-x.full.yaml
healthcheck:
test: ["CMD", "curl", "-sf", "http://localhost:9443/metrics"] //<<< use `/healthz` instead
interval: 5s
timeout: 3s
retries: 20
start_period: 10s
depends_on:
orderer-party1-assembler:
condition: service_healthy
Orderers now form per-party router->assembler->batcher chains, and every batcher depends on all 4 consenters. This makes sure we start servers in the recommended order.
Now that we have a health check resource on our operations endpoint (see #928) we can use it to start the docker compose network in the example in a correct way.
lets add to each service a
healthcheck, and explicitly encode the arma server dependencies withdepends_on.See:
https://github.com/hyperledger/fabric-x-evm/blob/main/compose.fabric-x.full.yaml
Orderers now form per-party router->assembler->batcher chains, and every batcher depends on all 4 consenters. This makes sure we start servers in the recommended order.