You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main package command line arguments are currently done in a mix of styles:
tcpaddr is an ip:port address with no default
raftaddr and raftport together form the bind location for the raft protocol
serfport is just the port with a default value -- the IP is hard-coded to 0.0.0.0.
raftdir is actually ignored, instead logdir/raftis always used
I propose getting rid of raftdir, and standardizing on ip:port arguments with defaults serving on all interfaces (0.0.0.0). Ideally the beginner, experimenting, can get started with a single-node cluster by just running jocko.
Would you accept a PR like this?
The text was updated successfully, but these errors were encountered:
Ah I ended up writing one. Let me know what you think about that. The Raft one has to be set to 127.0.0.1 and set at times when you want to advertise otherwise. Hashicorp's Consul works the same way.
The main package command line arguments are currently done in a mix of styles:
tcpaddr
is anip:port
address with no defaultraftaddr
andraftport
together form the bind location for the raft protocolserfport
is just the port with a default value -- the IP is hard-coded to0.0.0.0
.raftdir
is actually ignored, insteadlogdir/raft
is always usedI propose getting rid of
raftdir
, and standardizing onip:port
arguments with defaults serving on all interfaces (0.0.0.0
). Ideally the beginner, experimenting, can get started with a single-node cluster by just runningjocko
.Would you accept a PR like this?
The text was updated successfully, but these errors were encountered: