Describe the bug
With the size of the P-Chain at almost 20TB we are trying to partition out the Avalanche database so that older blocks can be stored on cheaper disk. We would like to run a node where the RPC is available but the node is no longer syncing, so that the node is effectively frozen at that point.
It appears that based on our configuration, the bootstrapping phase never ends. We get the following when we try RPC calls:
API call rejected because chain is not done bootstrapping
We have tried a number of configurations without success. Your help on a working configuration would be greatly appreciated.
Config
avalanchego \
--bootstrap-ips= \
--bootstrap-ids= \
--public-ip=127.0.0.1 \
--http-host=0.0.0.0 \
--http-port=9650 \
--network-health-min-conn-peers=0 \
--config-file /nodedata/avalanche/avalanche_config.json
{
"log-level": "debug"
,"snapshot-async": true
,"api-admin-enabled": true
,"api-health-enabled": false
,"index-enabled": true
,"api-info-enabled": true
,"api-ipcs-enabled": true
,"api-keystore-enabled": true
,"api-metrics-enabled": false
,"bootstrap-retry-enabled": false
,"db-dir": "/nodedata/avalanche/db"
,"chain-config-dir": "/nodedata/avalanche/chains"
,"http-host": ""
,"http-port": 9650
,"http-allowed-hosts": "*"
,"log-dir": "/nodedata/avalanche/logs"
,"network-id": "mainnet"
}
Logs
We are stuck here with this repeating over and over with forwarding chan message to consensus {"messageOp": "gossip_request"} and finished handling chan message {"messageOp": "gossip_request"}. Repeating between the output below.
[08-26|22:47:23.115] DEBUG <P Chain> bootstrap/bootstrapper.go:773 Checking for new frontiers
[08-26|22:47:23.115] DEBUG <P Chain> bootstrap/bootstrapper.go:256 sampled nodes to seed bootstrapping frontier {"sampledNodes": [], "numNodes": 0}
[08-26|22:47:23.115] INFO <P Chain> bootstrap/bootstrapper.go:273 bootstrapping skipped {"reason": "no provided bootstraps"}
[08-26|22:47:23.115] DEBUG <P Chain> bootstrap/bootstrapper.go:397 starting to fetch blocks {"numKnownBlocks": 99, "numAcceptedBlocks": 0, "numMissingBlocks": 99}
[08-26|22:47:23.116] DEBUG <P Chain> bootstrap/storage.go:195 executing blocks {"numToExecute": 0}
[08-26|22:47:23.116] DEBUG <P Chain> bootstrap/storage.go:187 executed blocks {"numExecuted": 0, "numToExecute": 0, "halted": false, "duration": "90.125µs"}
[08-26|22:47:23.116] DEBUG <P Chain> bootstrap/bootstrapper.go:738 waiting for the remaining chains in this subnet to finish syncing
[08-26|22:47:23.142] DEBUG <P Chain> handler/handler.go:888 forwarding chan message to consensus {"messageOp": "gossip_request"}
[08-26|22:47:23.142] DEBUG <P Chain> handler/handler.go:910 finished handling chan message {"messageOp": "gossip_request"}
[08-26|22:47:23.162] DEBUG <X Chain> handler/handler.go:888 forwarding chan message to consensus {"messageOp": "gossip_request"}
[08-26|22:47:23.162] DEBUG <X Chain> handler/handler.go:910 finished handling chan message {"messageOp": "gossip_request"}
[08-26|22:47:23.176] DEBUG <C Chain> handler/handler.go:888 forwarding chan message to consensus {"messageOp": "gossip_request"}
[08-26|22:47:23.176] DEBUG <C Chain> handler/handler.go:910 finished handling chan message {"messageOp": "gossip_request"}
[08-26|22:47:23.242] DEBUG <P Chain> handler/handler.go:888 forwarding chan message to consensus {"messageOp": "gossip_request"}
[08-26|22:47:23.243] DEBUG <P Chain> handler/handler.go:910 finished handling chan message {"messageOp": "gossip_request"}
[08-26|22:47:23.262] DEBUG <X Chain> handler/handler.go:888 forwarding chan message to consensus {"messageOp": "gossip_request"}
[08-26|22:47:23.262] DEBUG <X Chain> handler/handler.go:910 finished handling chan message {"messageOp": "gossip_request"}
[08-26|22:47:23.277] DEBUG <C Chain> handler/handler.go:888 forwarding chan message to consensus {"messageOp": "gossip_request"}
[08-26|22:47:23.277] DEBUG <C Chain> handler/handler.go:910 finished handling chan message {"messageOp": "gossip_request"}
[08-26|22:47:23.281] INFO <C Chain> core/state/snapshot/context.go:107 Generating state snapshot root=a53dc7..51ec2a in=1e3118..044749 at=7d91e5..bb9d62 accounts=10,773,879 slots=55,470,231 storage=4.58GiB elapsed=28m38.533s
Describe the bug
With the size of the P-Chain at almost 20TB we are trying to partition out the Avalanche database so that older blocks can be stored on cheaper disk. We would like to run a node where the RPC is available but the node is no longer syncing, so that the node is effectively frozen at that point.
It appears that based on our configuration, the bootstrapping phase never ends. We get the following when we try RPC calls:
We have tried a number of configurations without success. Your help on a working configuration would be greatly appreciated.
Config
Logs
We are stuck here with this repeating over and over with
forwarding chan message to consensus {"messageOp": "gossip_request"}andfinished handling chan message {"messageOp": "gossip_request"}. Repeating between the output below.