I'm running the tests from "chitchat-test" locally on my windows machine with the following script (trying to mimic the bash version as best I can):
Get-Process "chitchat-test" | Stop-Process
cargo build --release
for ($i = 10000; $i -lt 10100; $i++)
{
$listen_addr = "127.0.0.1:$i";
Write-Host $listen_addr;
Start-Process -NoNewWindow "cargo" -ArgumentList "run --release -- --listen_addr $listen_addr --seed 127.0.0.1:10002 --node_id node_$i"
}
Read-Host
Are the following results expected behavior, or am I maybe running into some windows bugs?
- The services started at 127.0.0.1:10000 and 127.0.0.1:10001 (before the seed address port) never receive any peers, and are stuck with a rather bare "state", regardless of how long I leave it running:
{
"cluster_id": "testing",
"cluster_state": {
"node_state_snapshots": [
{
"chitchat_id": {
"node_id": "node_10000",
"generation_id": 1711736008,
"gossip_advertise_addr": "127.0.0.1:10000"
},
"node_state": {
"chitchat_id": {
"node_id": "node_10000",
"generation_id": 1711736008,
"gossip_advertise_addr": "127.0.0.1:10000"
},
"heartbeat": 2,
"key_values": {},
"max_version": 0,
"last_gc_version": 0
}
}
],
"seed_addrs": [
"127.0.0.1:10002"
]
},
"live_nodes": [
{
"node_id": "node_10000",
"generation_id": 1711736008,
"gossip_advertise_addr": "127.0.0.1:10000"
}
],
"dead_nodes": []
}
The other services on ports greater than the seed start up fine.
- If I select a random process and kill it, all heartbeats stop (even for the services which received no peers). The state is still readable as JSON with a GET request to 127.0.0.1:10XXX, but the heartbeat does not increment, and no new peers are registered if I try adding them after the stoppage.
Is any of this expected behavior, or do we think maybe its windows related?
I'm running the tests from "chitchat-test" locally on my windows machine with the following script (trying to mimic the bash version as best I can):
Are the following results expected behavior, or am I maybe running into some windows bugs?
The other services on ports greater than the seed start up fine.
Is any of this expected behavior, or do we think maybe its windows related?