How to run stats slabs

marc,

I am guessing that you alread have a memcached bucket. You will have to telnet to the moxi to run stats slab.

Here is what you can do:

telnet 10.x.x.1 11212 (port where your memcached bucket is listening to)

stats slabs

Let me know how it goes.

Thanks

Bhawana

I never install Moxi as I didn't think it was needed, and I wasn't planning on using it.

So is Moxi needed?  My clients are all .Net based.

If it is just for debugging/management then I can get it installed on the Linux servers, but what about the Windows servers, is there a Moxi version for that environment?

thanks

marc

I upgarde the two node development membase envionment to 1.6.5 on Ubuntu.  I installed Moxi on both nodes, however, I'm not sure if I need to or how to configure it.

Do I need Moxi on both nodes or just one? How do Moxi to see both nodes in order to get the slab stats?

Also, what command do I run exactly.  I've tried stats slabs and stats slab, but all I get is an error message.

Can I access the membase servers on both nodes directly or do I alway now need to go through Moxi?

marc

marc,

You dont' need to install moxi separatley. It is one of the components that is bundled with your membase installation so it is already istalled on all your nodes. . The moxi can be client side or server side.  When your clients connect to port 11211, it is moxi they are connecting to (in a default configuration).

The moxi instances on all the nodes can communicate with each other. They are fully aware of the cluster configuration and adapt to the changes automatically. By default there is one moxi process running on each node at port 11211. This is called the gateway moxi. When you create another bucket on a different port, a new moxi process is spawned.

You can use either client side moxi or server side moxi. If your clients connect to localhost at port 11211 then you are using the client side moxi. The client side moxi  has information about the cluster configuration in addition to the vBucket mappings. Any cluster membership or health changes propagate automatically to the client-side Moxi's instances. The client-side Moxi server can reuse long-running connections (saving on TCP connection setup handshake time), and the client-side Moxi can multiplex multiple clients into share connections (reducing the file descriptor usage on the servers).

You will always use either the client side or the server side moxi to communicate with the Membase cluster. (except when you are doing cluster management). Please let me know if you have more questions and I will be glad to help.

The stats slabs is not working for me either. I am opening a Jira issue for that. I have also asked the Engineering team for a workaround if there is any, so that you are not blocked.

Thanks

bhawana

 Also Marc, are you using the Enyim client?  It has a stats interface that should allow you to specify 'slabs'.

Let us know if you need instructions on how to find that.

Perry

I was using the membase 2.10 .net client.  I'm working on trying to get the 2.11 .net client to work.

It looks like there are some undocumented changes that are breaking my code.

So far, the default name of the expected configuration section has changed, and for some reason the the NotFoundLocator is being created instead of the default node locator.

I'm not sure what is happening, I'm working through it now.

Does the stats interface in enyim also work in the membase client?

thanks

marc

 Yes, it should.  And you'll want to use the Membase configuration section within Enyim regardless of whether you're using a Membase bucket or a memcached bucket.

Let me know if you need some direct help with getting 2.11 to work.

Perry

Perry, what is the stats command I need to use with enyim?

Also, I'm going to open another thread about the issues I'm having with the enyim/membase 2.11 library.

thanks

marc

 I believe you'll want to use: client.Stats("slabs");

EDIT: Note that this command is not supported with Membase buckets since there are no slabs ;-)