Home | Forums | Membase | Membase Server 1.6.x

memcached connection

3 replies [Last post]
Fri, 01/28/2011 - 15:35
raanan.raz
Offline
Joined: 01/28/2011
Groups: None

Right now we are using a stand alone membase server.

For some reason the memcached process has around 3000 connections open and the w3p has 1500

The membase server itself has less than 10 requests per seconds (we haven't opened it to our production enviroment yet)

any ideas what could cause this huge amount of connections?

we have 21 worker processes which each 10 min/30 max pool to the membase server which means

it should go around 21*30 = 630 max connections..

we are using Enyim Memcached Client

Thanks!

 

 

Top
Sun, 01/30/2011 - 15:12
perry
Offline
Joined: 10/11/2010
Groups:

 Hi there, happy to try and help.

 

I believe this issue is being caused by not properly 'disposing' of your clients.  Check out the thread here: http://forums.membase.org/thread/northscale-client-100-cpu.  It's a slightly different symptom, but I think it's the same cause.

 

Let me know if that helps or if there is something else going on.

 

Thanks, take care.

 

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
Sun, 01/30/2011 - 23:46
raanan.raz
Offline
Joined: 01/28/2011
Groups: None

Thanks Perry

I will check that out and let you know.

I have added .dispose on the Membase Client at Application_OnEnd event.

 

Thanks again!

Top
Mon, 01/31/2011 - 03:45
raanan.raz
Offline
Joined: 01/28/2011
Groups: None

Hi,

The Application_OnEnd wasn't the issue (i also checked manually and this wasn't the case).

We have figured out the problem and it goes something like this..

We have a template class  that handles

public class CacheManager<T>
{
    static MembaseClient memClient = new MembaseClient();

    // Wrapper functions

}

What could be the problem with this? :)

well.. as it turns out.. we forgot that a each template class creates a unique instance

hence, if we have 10 different objects, it will cause 10 classes and the pool will be 10x greater..

we have worked it out by creating:

public class MembaseWrapper
{
    public static MembaseClient memClient = new MembaseClient();
}

public class CacheManager<T>
{
    // We use MembaseWrapper.memClient   
}

 

hope this helps anyone.

 

 

Top