Couchbase
  • Why NoSQL?
  • Couchbase Server
  • Download
  • Resources
  • Careers
Home | Forums | Membase | Membase Server 1.6.x

So Confusing,Who Can explain the terms of monitoring for me?

2 replies [Last post]
  • Login or register to post comments
Mon, 05/09/2011 - 23:13
haoguoliang
Offline
Joined: 04/28/2011
Groups: None

Resident item ratio

Replica resident item ratio

Disk write queue size

Disk fetches per sec

Items persisted per sec

RAM ejections per sec

OOM errors per sec

Temp OOM errors per sec

Connections count

CAS hits per sec

CAS badval per sec

CAS misses per sec

VBucket errors per sec

Top
  • Login or register to post comments
Tue, 05/10/2011 - 11:18
mikew
Offline
Joined: 03/14/2011
Groups:

Resident item ratio - The amount of active key-value pairs that are in memory.

Replica resident item ratio - The amount of replica key-value pairs that are in memory.

Disk write queue size - The amount of items that are waiting to be persisted to disk.

Disk fetches per sec - The amount of items that are being read from disk and brought into memory.

Items persisted per sec - The amount of items that are persisted to disk per second

RAM ejections per sec - The amount of items that are being kick out of memory to make room for items that have been fetched from disk

OOM errors per sec - The amount of keys-value pairs per second that could not be put into memory because there wasn't enough room. If this happens it means that you need to add more memory to your cluster because the key meta data has filled ram and values cannot be added to ram. This could happen if the amount of key-value pairs in your system is very large and your cluster memory is small in comparision.

Temp OOM errors per sec - This is similar to OOM errors, but not necessarily bad. It means that we are ejecting key-value pairs from memory and we can't handle your request right now. Try again later and it should work. In this case your client should exponentially back-off and the operation should eventually succeed. These should be rare.

Connections count - The amount of incoming connection to a Membase server

CAS hits per sec - The number of cas operations that have succeeded and the key-value pair was in memory.

CAS badval per sec - The number of cas operations that have failed because of a bad cas value

CAS misses per sec - The number of cas operations that have succeeded but the key-value pair was not in memory and had to be fetched from disk

VBucket errors per sec - The number of times a key-value pair was not on the server it was sent to and had to be redirected to the correct server in the cluster.

Top
  • Login or register to post comments
Wed, 05/11/2011 - 22:23
haoguoliang
Offline
Joined: 04/28/2011
Groups: None

Thank you for your reply!

Top
  • Login or register to post comments
  • Login or register to post comments
  • Login
  • Register

Company

  • About Us
  • Leadership
  • Customers
  • Partners
  • Contact Us

Product

  • Couchbase Server
  • Couchbase SDKs
  • Use Cases
  • Documentation
  • Forums

Open Source

  • Couchbase Project
  • Couchbase vs. CouchDB

Commercial

  • Subscriptions & Support
  • Training & Services

News

  • Blog
  • Newsletter
  • Press Releases
  • Buzz

Follow Us

    
  • Customer Login
  • Terms of Service
  • Privacy Policy
  • Trademark Policy
  • Site Map

© 2013 COUCHBASE All rights reserved.

Sign in to Couchbase Community

close
  • Create new account
  • Request new password
You are logging into the Forums, Wiki and Issue Tracker