Home | Forums | Membase | Membase Server 1.6.x

Does port 11210 serve diffrent protocal from 11211

2 replies [Last post]
Mon, 01/31/2011 - 02:20
persanker
Offline
Joined: 01/31/2011
Groups: None

[root@localhost bin]# memcat --servers=192.168.1.229:11211 test
test

[root@localhost bin]# memcat --servers=192.168.1.231:11210 test 
(block here...)

why?

Top
Mon, 01/31/2011 - 05:47
alkondratenko
alkondratenko's picture
Offline
Joined: 12/01/2010
Groups: None

 --binary would work. But note that you need vbucket-aware client to correctly interoperate with membase rebalancing & replication. Moxi is vbucket-aware as well AFAIK .net & java clients. There's also libmembase.

Top
Mon, 01/31/2011 - 19:17
perry
Offline
Joined: 10/11/2010
Groups:

 Yes, to follow up, port 11210 is our Membase-native port and requires a client to be vbucket-aware.  If you are using a standard memcached client, you'll need to go through a Moxi process (either on the client-side or the server-side) in order to properly access the data.

 

Clients such as the Enyim client, upgraded spymemcached or libmembase will allow you to access port 11210 directly.

 

Perry

__________________

Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Couchbase: http://www.couchbase.com/products-and-services/overview
Call or email "sales -at- couchbase-dot- com" today!

Top