Home | Forums | Couchbase | Couchbase Server 1.8.x

1.8 admin panel keys

3 replies [Last post]
Tue, 06/19/2012 - 06:15
testarc
Offline
Joined: 05/08/2012
Groups: None

Hello all,
In couchbase 2.0 dev preview there is a panel which i can see all stored keys in the server with 5 items in each page. I couldn't find this on 1.8 panel is it a new feature? For debugging purposes i will need this a lot.

Top
Tue, 06/19/2012 - 11:08
BigBlueHat
Offline
Joined: 01/28/2011
Groups: None

testarc,

Couchbase Server 2.0 includes an HTTP API similar to the one in Apache CouchDB, and that's what the 2.0 Admin UI uses to let you browse through the stored docs/values in each bucket. 1.8 does not have an HTTP API, but you can use the memcached API to access keys and get the values of one or more keys at a time. However, there is no way to access "all docs" style output from the memcached protocol.

Couchbase 1.8 does include an unsupported feature known as the TAP Protocol which allows you to observe changes made to the database.

Additionally, you can use the the `cbc` command line tool that ships with libcouchbase top check the values of keys and get cluster wide statistics such as how many items are in the cluster. If you're mainly trying to confirm that keys were stored, then the following command might be helpful:

$ cbc status | grep items

That will show you output similar to this (my bucket is empty, however):

127.0.0.1:11210	curr_items	0
127.0.0.1:11210	curr_items_tot	0
127.0.0.1:11210	vb_active_curr_items	0
127.0.0.1:11210	vb_replica_curr_items	0
127.0.0.1:11210	vb_pending_curr_items	0

Hopefully something in there is helpful. :)

Later,
Benjamin

Top
Tue, 06/19/2012 - 17:48
sjpark9
Offline
Joined: 03/01/2012
Groups: None

[quote=BigBlueHat]
Couchbase 1.8 does include an unsupported feature known as the TAP Protocol which allows you to observe changes made to the database.

Why is TAP Protocol unsupported? I've checked the document and seems like very useful thing for the users.

Having hard time figuring out how to use each apis and etc. due to lack of examples....

Is there any reason that couchbase lacks examples or guideline to how to use couchbase, etc.?

Top
Wed, 06/20/2012 - 10:42
ingenthr
Offline
Joined: 03/16/2010
Groups:

TAP is unsupported at the moment because it's still an 'evolving' interface to the system. There are particular requirements of TAP clients that, if not handled properly, can lead to unexpected resource usage on the server and then impact the primary workload the server is expected to perform. I'm sure you can understand that we want to be sure that if you use TAP, it won't cause an unexpected drop in performance on other parts of the system.

We definitely want to get something in place to meet the need of iterating/dumping all of the data from the system and are working to do so. Please look out for the updates.

On the use of APIs and examples, have you found the SDK manuals along with the example applications at http://www.couchbase.com/docs ? What kind of examples have you been seeking that you've not been able to find?

Top