Home | Forums | Membase | Membase Server 1.6.x

Lazy flush doesn't work

1 reply [Last post]
Wed, 12/08/2010 - 08:16
wirfeon
Offline
Joined: 12/08/2010
Groups: None

Hello.

I have a cluster consisted of 2 servers. There is a membase bucket which resides on both servers. My client is using memcache protocol and it is connected to the bucket via stand-alone moxi. The client is supposed to store an infinite numbers of keys. Before the bucket hits its RAM quota, it manages to store around 3M keys. Then the client sends a flush_all command and  it properly invalidates all of the keys. When i run the client again, it manages to store only 100k keys a then it throws an error:

[NOTICE@1291817675.774581] mcm_storage_cmd():3344: unable to store value: Interrupted system call: temporary failure

I think, that there is a problem with that lazy flushing. It looks like that membase doesn't free the memory at all... When I restart the server the bucket is empty again.

This problem also appears on server-side moxi.

There is no problem with memcache bucket. Flushing works fine there...

Membase server is 1.6.0.1 64bit and running on Debian GNU/Linux 5.0

Moxi is 1.6.0.1 64bit

Client is using memcache C API 1.4.0.rc2-1

 

Can someone point me to the right direction please?

Thank you.

Top
Wed, 12/08/2010 - 12:50
bhawana@membase
Offline
Joined: 10/29/2010
Groups: None

Can you please send to me the output of the following command before and after the flush_all: /opt/membase/bin/ns_server/collect_info Thanks Bhawana

__________________

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 Membase: http://www.membase.com/products-and-services/overview
Call or email "sales -at- membase -dot- com" today!

Top