RavenDB 4.0, EnsureConnectedNow waits forever

[Derek den Haas]

var changes = _store.Changes("DatabaseName");

await changes.EnsureConnectedNow();

I first thought it was because I didn't expose port 38888, so made sure I did. As far as I can see, the code is implemented on the client side, but is it already working? Or am I using a feature that isn't there yet?

[Derek den Haas]

Since I didn't state the version: 4.0 Nightly 2017-10-19

Op donderdag 19 oktober 2017 17:34:15 UTC+2 schreef Derek den Haas:

[Derek den Haas]

Got it working... it tries to bind on port 38888, which was blocked internally, saw another issue:
https://groups.google.com/forum/#!searchin/ravendb/In$20rehabilitation$20because$20the$20last$20report$20status$20was$20%22WaitingForResponse%22%7Csort:date/ravendb/kRS7Nh7_epo/idyZqPcZAwAJ

[Oren Eini (Ayende Rahien)]

I'm not sure that I'm following.

Port 38888 is typically the TCP port, but changes uses a web socket.

What was the issues?

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

 

On Thu, Oct 19, 2017 at 7:03 PM, Derek den Haas <derek...@gmail.com> wrote:

Got it working... it tries to bind on port 38888, which was blocked internally, saw another issue:
https://groups.google.com/forum/#!searchin/ravendb/In$20rehabilitation$20because$20the$20last$20report$20status$20was$20%22WaitingForResponse%22%7Csort:date/ravendb/kRS7Nh7_epo/idyZqPcZAwAJ

--
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.

[Derek den Haas]

RavenDB itself was in REHAB mode, since it couldn't access it's own server (I think it's trying to access port 38888, at least I hope so, else I have no clue why it's working now):

In kubernetes inside a deployment you have to tell it to open port 8080 and 38888, (like the docker -p 8080:8080 38888:38888), which was done for the 8080 but not for the 38888, since I never knew what it was for. When enabling 38888, it is accessible from the outside of the container, since the used PUBLIC_SERVER_URL was pointing to it's outside 10.0.0.9 IP address (at least, that is where the DNS record was pointing to) (not 127.0.0.1). From what I was reading in the other thread, when not being able to find itself by it's URL it is getting in REHAB mode, and doesn't do subscribtions / changes.

After opening up port 38888, raven found itself and is now "GREEN" (MEMBER), not in REHAB.

Op donderdag 19 oktober 2017 21:54:03 UTC+2 schreef Oren Eini:

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

[Oren Eini (Ayende Rahien)]

Okay, thanks for the explanation

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