Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Volume stores from remote nodes aren't correctly identified. #186
I setup a (self-compiled) installation of version 0.70 beta linux amd64, on a pair of nodes:
The clients were started like this:
This resulted in the two volume-servers connecting to the single-master, as expected, however the logging on the master showed connections from:
This meant that the master could only talk to one of the volume-servers, and thus all uploads failed because I'd mandated replication such that writes went to both.
To resolve this problem I had to explicitly set the hostname/IP address of the volume-servers:
Did I miss an important piece of documentation, or does this seem like a bug? Looking at the code I see
So clearly the behaviour I'm seeing comes from that - if I don't set an IP explicitly it defaults to local-host which isn't going to work in a real deployment. I updated that code to use that from here, and things started working as expected:
Feedback/corrections welcome. Thanks for the great project, too, lest you think I'm just complaining without appreciating your enormous effort!
Thanks for such a long and detailed writing!
The default values are just for playing around at first, not in real production.
I bet you are not setting up production servers, but just trying it. Do you want to fail fast and find out this setup issue now or after it's a few days on production?
Some computer has multiple IP addresses, or IPv6 plus IPv4, or IPv6 only. Relying on guessing one of them is not helping production cases. Your network may change one day. The guessed value also depends on ordering. So someday the server may start fine, someday the server can not work...
So I prefer fail fast and require users have to explicitly set production values themselves. The guessing magic may give users a false sense of "correct setup".