after remove a node with garage layout remove <node id>, the remaining nodes are still trying to connect to that node
Are all of you guys using Consul or Kubernetes discovery ? Ping @jpds @kristof.p @flamingm0e @tradingpost3
7a9f1fadad
Merge branch 'main' into next-0.10
7be3f15e45
Merge pull request 'import Netapp code into Garage codebase' (#717) from import-netapp into main
125c662860
[import-netapp] move and rename FullMeshPeeringSrategy to PeeringManager
5766befb24
[import-netapp] fix tests
5ea24254a9
[import-netapp] import Netapp code into Garage codebase
7be3f15e45
Merge pull request 'import Netapp code into Garage codebase' (#717) from import-netapp into main
125c662860
[import-netapp] move and rename FullMeshPeeringSrategy to PeeringManager
5766befb24
[import-netapp] fix tests
5ea24254a9
[import-netapp] import Netapp code into Garage codebase
import Netapp code into Garage codebase
125c662860
[import-netapp] move and rename FullMeshPeeringSrategy to PeeringManager
5766befb24
[import-netapp] fix tests
5ea24254a9
[import-netapp] import Netapp code into Garage codebase
a2ab275da8
Merge pull request 'Fix cargo warnings in Cargo.toml files' (#718) from fix-cargo-toml into main
1b0f167d2f
[fix-cargo-toml] fix cargo warnings in Cargo.toml files
a2ab275da8
Merge pull request 'Fix cargo warnings in Cargo.toml files' (#718) from fix-cargo-toml into main
1b0f167d2f
[fix-cargo-toml] fix cargo warnings in Cargo.toml files
Fix cargo warnings in Cargo.toml files
Fix cargo warnings in Cargo.toml files
c6c3694263
[import-netapp] move and rename FullMeshPeeringSrategy to PeeringManager
65481f32e0
[import-netapp] fix tests
5d41fb01b8
[import-netapp] import Netapp code into Garage codebase
adce32ec87
[import-netapp] move and rename FullMeshPeeringSrategy to PeeringManager
e79e303dde
[import-netapp] fix tests
31c6798d68
[import-netapp] import Netapp code into Garage codebase
cf2af186fc
Merge branch 'main' into next-0.10
db48dd3d6c
bump crate versions to 0.10.0
segfault after unexpected server reboot