Membase using Enyim went crazy
Hi guys,
I've started developing a social game using Membase in .NET (using Enyim's .NET API) - now it all worked fine and dandy until suddenly Enyim couldn't communicate with my Membase server anymore - this forced me to uninstall and re-install Membase.
Now it worked fine for about 2 weeks until today it happened again - every time I attempt to read/write to/from Memabse, it waits for 10 seconds (my idle time and then returns null or doesn't write).
Looking in the Membase management console I see 0 activity on it.
Keep in mind that the code is fine and worked 100% yesterday, and today by simply rerunning the code, it's not working.
Nothing had changed.
Please help!
I'd need to look at the logs to know more, but it is possible that the IP address of your server(s) is/are changing because of DHCP?
If you log into the Membase console and go to "Servers", does the IP address listed there match the actual IP of the server?
http://forums.membase.org/thread/issues-dhcp-development-laptop
Perry
Well unfortunately I got sick of waiting for help because I needed to continue developing, but like I said this is the 2nd time this has happened.
The server runs on localhost as this is our development server, and all addresses pointing to it uses localhost and not a static IP.
And have you specifically configued Membase to use localhost? What does the Membase UI say in the Server list?
Nice catch, it actually uses the DHCP IP that our office router gives the server, however, won't localhost point to that same IP address if it changes?
If you configure Membase to use localhost (http://techzone.couchbase.com/wiki/display/membase/Using+Membase+in+the+...) then it will actually register the node as "localhost" and any change to the underlying IP will be transparent.
However, this only works for a single node and cannot be used to cluster multiple nodes together. You will either need to use servers with static IP's or provide externally accessible DNS names for all the nodes in the cluster.
Perry
Oh yea, also when I attempt to connect via telnet directly to Membase (this used to work before - telnet localhost 11211) everything I type in it simply writes "ERROR".