Home | Forums | Couchbase | Couchbase Server 1.8.x

incorrect watermark update ?

3 replies [Last post]
Tue, 01/29/2013 - 21:14
fahd
Offline
Joined: 01/29/2013
Groups: None

I was adjusting the watermark values, and the result was not at all what I attempted to set it to be.

Pre update:
ep_mem_high_wat: 70297583616
ep_mem_low_wat: 56238066888

# /opt/couchbase/bin/cbflushctl mb-bidseg-01-01:11214 set mem_high_wat 80000000000
setting flush param: mem_high_wat 80000000000
# /opt/couchbase/bin/cbflushctl mb-bidseg-01-01:11214 set mem_low_wat 70000000000
setting flush param: mem_low_wat 70000000000

root@mb-bidseg-01-01:~# /opt/couchbase/bin/cbstats mb-bidseg-01-01:11214 all| grep mem
ep_diskqueue_memory: 0
ep_mem_high_wat: 138581319680
ep_mem_low_wat: 116865055740

all stats before change: http://pastebin.com/MMMXYb7q
all stats after change: http://pastebin.com/6TUKjVFS

Top
Wed, 01/30/2013 - 12:47
mikew
Offline
Joined: 03/14/2011
Groups:

Can you try to go through port 11210 and use the options to specify which bucket. I believe the option is -b . For example

/opt/couchbase/bin/cbflushctl mb-bidseg-01-01:11210 set mem_high_wat 80000000000 -b bucket1

Top
Wed, 01/30/2013 - 12:55
fahd
Offline
Joined: 01/29/2013
Groups: None

# /opt/couchbase/bin/cbflushctl mb-bidseg-01-01:11210 set mem_high_wat 80000000000 -b cookie-segments
Usage: cbflushctl [options]

cbflushctl: error: no such option: -b

http://www.couchbase.com/docs/couchbase-manual-1.8/couchbase-admin-cmdli...

# /opt/couchbase/bin/cbflushctl mb-bidseg-01-01:11210 set mem_high_wat 80000000000 cookie-segments
setting flush param: mem_high_wat 80000000000

# /opt/couchbase/bin/cbflushctl mb-bidseg-01-01:11210 set mem_high_wat 70000000000 cookie-segments
setting flush param: mem_high_wat 70000000000

# /opt/couchbase/bin/cbstats mb-bidseg-01-01:11214 all|egrep "ep_mem|mem_used"
ep_mem_high_wat: 196865055744
ep_mem_low_wat: 116865055740
ep_mem_tracker_enabled: true
mem_used: 69110322240
root@mb-bidseg-01-01:~# /opt/couchbase/bin/cbstats mb-bidseg-01-01:11210 all|egrep "ep_mem|mem_used"
ep_mem_high_wat: 78643200
ep_mem_low_wat: 62914560
ep_mem_tracker_enabled: true
mem_used: 57182968

ok, so that worked. What is it reporting when I query on :11214 ?

Top
Mon, 02/04/2013 - 18:23
mikew
Offline
Joined: 03/14/2011
Groups:

The problem is that your going through the proxy server (moxi) and the proxy is trying to aggregate all of the responses from each server. I think what happens is that everything is just added together and this makes some of the stats look incorrect. I'm going to discuss this with our products team and figure out if we want to disable this from happening or to just make improvements in this area. You can track the issue here if you would like.

http://www.couchbase.com/issues/browse/MB-7678

Also, the -b parameter is now used in 2.0. Sorry for the confusion.

Top