can't add third node when following steps for creating cluster in Book Ch. 6

[Matthew Dennis]

After I add the second node, both nodes are Voting and adding a third node fails due to lack of Leader.  Neither node is marked as Leader.

In fact it appears that all cluster related functionality fails due to lack of leader.

Build 40025, Version 4.0, SemVer 4.0.0-rc-40025, Commit ad047bc

[Matthew Dennis]

I found the issue.  The Book says to start the second node with

./Server/Raven.Server.exe --ServerUrl=http://127.0.0.2:8080 --Logs.Path=Logs/B --DataDir=Data/B

but it should be

./Server/Raven.Server.exe  --ServerUrl=http://127.0.0.2:8080 --ServerUrl.Tcp=tcp://127.0.0.2:38888 --Logs.Path=Logs/B --DataDir=Data/B

Otherwise it listens on 127.0.0.1:38888 

[Matthew Dennis]

Also, the online documentation says

TcpServerUrl=tcp://0.0.0.0:38888

not ServerUrl.Tcp=tcp://0.0.0.0:38888

[Matthew Dennis]

According to the documentation, this should not be required as the TCP url should be built from the Http url if the TCP url is not provided, however it is not working correctly.

[Oren Eini (Ayende Rahien)]

Thanks

http://issues.hibernatingrhinos.com/issue/RDoc-1095

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Oren Eini (Ayende Rahien)]

Yes, it should be automatically retrieved, we'll check this

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

[Matthew Dennis]

On Tuesday, January 16, 2018 at 10:48:28 PM UTC-5, Matthew Dennis wrote:

[Oren Eini (Ayende Rahien)]

Can you try this with the latest nightly?

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

[Matthew Dennis]

I did.  

• without the --ServerUrl.Tcp=..., when the second node is added a Leader can't be found.
• with the --ServerUrl.Tcp=..., when the second node is added a Leader is chosen and I can now add the third node.
  

I thought it might be that the Uri.DnsSafeHost property, used to create the TCP endpoint if the ServerUrl.Tcp is not specified, was returning the same value for 127.0.0.X, but a simple test showed this was not the case, so the bug for creating the default ServerUrl.Tcp lies elsewhere.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

[Matthew Dennis]

I double checked with the RC and even with the corrected tcp url, the cluster failed to agree on a Leader after the second node was added.  Going to the nightly build resolved the issue, as it did yesterday.

Thanks

http://issues.hibernatingrhinos.com/issue/RDoc-1095

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

[Matthew Dennis]

I double checked with the RC and even with the corrected tcp url, the cluster failed to agree on a Leader after the second node was added.  Going to the nightly build resolved the issue, as it did yesterday.

On Wednesday, January 17, 2018 at 2:24:30 AM UTC-5, Oren Eini wrote:

Thanks

http://issues.hibernatingrhinos.com/issue/RDoc-1095

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

[Oren Eini (Ayende Rahien)]

Hi,

Just to let you know, I just verified that this works without ServerUrl.Tcp in the current release.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.