We are having a single node Couchbase *[4.5.1-2844 Community Edition (build-2844)]*. For some reason, we are seeing high memory usage on the server. When we log into the server and view the stats we can see that **memcached** and **beam.smp** service is using the memory. I need to know, what is the use of **beam.smp** process, and why it is consuming high memory. Screenshot for the same is attached to the question. Also I have followed the following links to debug the issues: https://forums.couchbase.com/t/beam-smp-memory-usage/11843/2 https://issues.couchbase.com/browse/MB-20521

Whats the exact algorithm to calculate the CouchDB revision number. CouchDB uses a deterministic algorithm to calculate the document revision number. Here is one relevant doc I found: https://stackoverflow.com/questions/5954864/how-does-couchdb-calculate-the-revision-number Buts its all in elrang, I am trying to implement it in dart. I use sample document : {"_id":"123-this-is-an-id","hello":"world","testing":123} for testing. When I do the MD5 hash of it , its gives me : f0853833850bce08dce0896e010a375e, where as the couchdb revision number is : "_rev": "1-43dce8fe7e9a26b49390e3727a015cc0" I google it everywhere, but if I can find the algorithm some where in text , UI can convert it into dart.

cbrestore runs without error messages, but does not transfer any data. The problem occurs on debian 10 with couchbase versions 6.0.0, 6.0.1, 6.0.3. The exactly same command runs without problems on windows 10 with couchbase version 6.0.1 - with the same dump.

Couchbase's documentation on GSI states that *Global Secondary Index is a powerful solution for secondary lookup queries that are required for interactive applications that require low latencies.* The documentation also mentions that GSI has good write performance, so I am wondering if there are use cases (besides requiring MapReduce aggregations) where Views would be preferred.

I was exploring couchbase backup and restoring procedures then we found standard procedures. But, if I can take data directory backup in the form of .tar and untar data directory whenever restore required, will it work? tar -cvf /opt/couchbase/var/lib/data -----backup tar -xvf xxx.tar ----restore

I have 3 node couchbase cluster which is working fine but now days I am getting many alerts as "Metadata overhead warning. Over 54% RAM allocated to bucket" on couchabse web UI. Please help to supress these alert

I have just started using couchbase server and trying to configure backup and restore method. We require to take backup for each couchbase node or cluster backup also available ?

i am working on a POC where i need to implement same like SSIS for sql to hadoop. out DW are in SQL Server and we want to create a HBase at central location where all the data from diff DW will be posted. for the first time load i can do it using "sqoop import" command. but after then for changed data how to do incremental of sqoop with HBase?

I am evaluating best database solution for a sizeable application. My basic requirements include: - Data should be encrypted at disk level - Mobile support - Scalable - Enterprise support I realized Couchbase Server solution would be sufficient for my requirements. I've tested some of the above with Couchbase Server and got stuck on how data encryption on Couchbase Server is applied. I could find only few high level documentation related to this topic. Including below official documentations - Encryption at Rest They say there are 4 possible third party encryption tools that can be used: - Linux Unified Key Setup (LUKS) - Vormetric - Gemalto - Protegrity But they are not explaining on how to use or configure the above tools. **Question 01** What would be the best recommended encryption tool out of above? **Question 02** Is there any documentation(with samples) on how to setup encryption on Couchbase Server?

I have a couchbase bucket, in it I have an Integer data with a key. I am incrementing it, using the API "increment" so I cannot put a JSON there with the date of the last updated. The question is, how can I select ALL element that where changed today/yesterday?

Need help regarding backup validations for couchbase, what is the best way / easiest way to validate couchbase backups. we have recently moved to couchbase and totally new to couchbase, having some trouble with backup validation. we are using **cbbackupmgr** backup for taking backup's and tar the backup file at the end, could not find any solution on my research. Any help from this community, Thanks in advance.

I'm working on a small project which would involve running queries against deeply-nested (up to 5 layers) keys in dictionaries. This would be specifically a read-heavy environment, with only one large set of rites during the app's bootstrapping (nominally once per install). The two options I'm considering for use as database backends right now are PostgreSQL (10.0) and Couchbase (5.0.1). I'm reasonably familiar with Postgres and its JSONB facilities in terms of performance (although not implementation details), but I'm not familiar enough with Couchbase to draw a concrete comparison, and it's difficult to find this specific comparison in any online benchmarks. Ignoring issues about the fact that Postgres isn't a document store, could Postgres consistently outperform Couchbase in read queries involving accessing a deeply-nested key/value pair?

After creating a CouchBase dump and copying it to a Google Storage bucket I tried importing the data to BigQuery. I failed miserably, apparently the design.json or the files that appear in the same directory as data-0000.cbb are not working when I'm trying the json import. Do I need to convert the dump somehow? Is there any other way to migrate the data from CB to BQ? Thank you all in advance.

Is there a way we can get a document's creation date in Couchbase (2.2.0). We are currently not storing creation date in our documents, so wanted to know if couch stores that as part of document meta data. We plan to query documents based on time, and currently the only option that we think will work is to change the server code to store additional creation date field as part of the document itself.

How should the logical type of a document get specified in CouchBase? Using a field for the type? Or employing separators in keys like product::app::123id? Currently I'm putting a document type, inside the document itself, inside a string field named Type like say Product. But I see this pattern of using separators in document id, like product::app::123id. Done some playing around it, couldn't get the type part (product) from the key (Of-course parsing it, by splitting is possible, which to me seems to have same overhead in both N1QL and views). So how should the document type (app logic type) get specified? Env: CouchBase Community, inside Docker on Ubuntu 14.04, using Go client gocb.

As the title said, when is the time that Couchbase write documents to disk? every 60 seconds? every 1 seconds? every 100 ms? or everytime there are read command to that document?

So currently this is a common setup: > Client -> Ajax -> Server CRUD -> Database Does Couchbase allow me to do this? > Client -> Ajax -> Database This might be more technically correct: > Client -> Ajax REST -> Database Does this mean that I could just have the client directly interacting with the database, therefore reducing the load on the server? Theoretically this would make scaling a website more cost efficient. If so, has this method been increasing in popularity usage? If not, why? It seems like this is a huge advantage.

I see a massive gap of popularity between MongoDB and Couchbase. **What features\advantages does mongo have over couchbase?** I'm deploying DB instances in a cluster, between datacenters, where all servers accept incoming requests. Is it not simpler to do this with couchbase, that has only one server role, and less configuration?

**Background Information** This is day one for me with couchbase. I've been reviewing the sample databases using the database console that comes with couchbase. Specifically, I've been playing with the "beer-sample" application to try to understand how to organize my database. It seems that they have two different types of documents - breweries or beers - and everything is just in one bucket. For my personal application, I have the following data: { "server_details": { "name": "testserver", "dns_name": "testserver.mydomain.net", "ipv4": "10.xx.xx.xx", "ipv6": "", "type": "webserver" }, "server_status": { "up_to_date": true }, "packages": { "package1": { "current_version": "x.x", "previous_version": "x.x", "last_updated_on": "2016-03-16", "play_id": "link to audit table" }, "package2": { "current_version": "x.x", "previous_version": "x.x", "last_updated_on": "2016-03-16", "play_id": "link to audit table" } } } I have different server types such as webserver, appserver, dns server etc. So I'm planning to just use the same json object but change the "type" field. **Question** I also need to create some sort of a audit table that will show the history of when a package on a server was updated. I need to track things like: - execution date - script name - package1_version_b4_update - package1_version_after_update - server_dns_name This is the json object I've come up with for this type of a document: { "audit_details": { "script_name": "upgrade_all_mrts", "rt_ticket_number": "16123", "execution_date": "2016-03-16", "status": "success" }, "affected_servers": { "server1": { "package1":{ "version_after_update": "x.x", "version_before_update": "x.x", "last_updated_on": "2016-03-16" }, "package2": { "version_after_update": "x.x", "version_before_update": "x.x", "last_updated_on": "2016-03-16" } }, "server2": { "package1":{ "version_after_update": "x.x", "version_before_update": "x.x", "last_updated_on": "2016-03-16" }, "package2": { "version_after_update": "x.x", "version_before_update": "x.x", "last_updated_on": "2016-03-16" } } } } Would this be just another document with a completely different structure? or should i be putting it in another bucket? If it should all be in the same bucket, is the structure of the json object I'm proposing appropriate? Fundamentally, I guess my question is do you dump everything into one bucket as a collection of varied documents... and just make sure that the related documents have the same structure so that you can query them all at once? Sorry for the remedial questions but I'm try to build a prototype on the fly ...while reading the docs. Any tips would be appreciated.

Is it possible to validate the data before it is entered into couchbase? I did not find any documentation confirming this. But I believe there must be some way to do it.