This is the Beta release of Couchbase Server 2.0. Couchbase Server 2.0 is the next major version of Couchbase Server. The 2.0 version adds support for distributed indexing and query, real-time map/reduce functions and cross-data center replication. Couchbase Server 2.0 builds on the high performance Simple, Fast, and Elastic Couchbase Server 1.8. The beta release is available to all enterprise- and community-edition customers. For more information about Couchbase Server 2.0, visit Couchbase Server 2.0.
New Features and Behaviour Changes in 2.0.0
Two sample databases can be loaded either during setup or in the setting panel.
Advanced indexing configuration can be updated in the Couchbase Admin console including maximum number of index building tasks that are executed in parallel.
Design documents for active data are automatically indexed when a threshold on time is met or a number of document mutations is reached. This is user configurable.
For more information, see 「インデックスの自動更新」.
New statistics have been added to understand the cross data center replication streams. The source cluster will show information about each XDCR including document mutation to be replicated.
For more information, see 「バケットとクラスタの統計の表示」.
Backup and Restore support is now available.
For more information, see 「バックアップとリストア」.
Debug information has been added into the view and indexing
operations to make debugging views easier. You can enable this
by using debug=true as query parameter.
E-mail alerts can now be created when certain error situations are encountered in a cluster.
For more information, see 「アラートの有効化」.
You can now manually compact data and design documents using the admin console.
For more information, see 「ビューエディタの利用」.
Database Operations
Provide return value of 'not found' in response to get operations on document that does not exist.
Enable sending compression option as parameter for a document to Couchbase Server.
Issues: MB-6482
Cluster Operations
Fixed incorrect message, 'There are currently no documents in this bucket.' to 'there are currently no documents in this bucket corresponding to the search criteria.'
Issues: MB-6442
Fixed rebalance failure. Rebalanced had stalled after performing failover and removing node due to memory leak on cluster nodes.
Issues: MB-6550
Web Console
Fix Couchbase Admin Console layout when a design document or view has a long name.
Issues: MB-5465
Corrected intermittent failures occurred when loading sample data via setup wizard or the Settings tab on MAC when user starts couchbase server app for the first time. Occurred due to some permission issues.
Issues: MB-6452
Corrected wrong build number displayed in Mac OS X builds in dialog box.
Issues: MB-6668
Fix Couchbase Admin Console behavior when failover is in progress and node goes offline.
Issues: MB-4756
Command-line Tools
Restore connection to hostname instead of IP address.
Issues: MB-6470
Indexing and Querying
Compaction file for views had been deleted if the process for index compaction died.
Deleting design documents in development resulted in deleting production index files.
Issues: MB-6517
Cross Datacenter Replication (XDCR)
Installation and Upgrade
It is not possible to perform an upgrade between Couchbase Server 2.0 pre-releases including beta, or to perform an offline upgrade from Couchbase Server 1.8 to a pre-release or beta of Couchbase Server 2.0. To upgrade between these versions use cbbackup to backup your data, delete the existing installation, install the new version, and restore the stored data.
For more information, see 「バックアップとリストア」, 付録B Couchbase Serverのアンインストール.
An upgrade path is not supported to the beta release from prior developer preview builds. You need to uninstall your developer preview release and install the new release.
Documents identified as Non-JSON stored within Couchbase Server may appear as binary, or text-encoded binary data within the UI.
Issues: MB-7069
During periods of moderate CPU load on the Couchbase Server
cluster, you may see warnings that IP address seems to
have changed. Unable to listen to node X.X.X.X.
Database Operations
Cluster Operations
Rebalance fails with error "bulk_set_vbucket_state_failed" due to timeout in tap_replication_manager for default bucket.
Issues: MB-6595
One of the internal maintenance processes within Couchbase Server for checking vBuckets will stop node rebalance when you create replication via XDCR on a source cluster.
A node in a cluster may also stop rebalance when another node orchestrating rebalances is over loaded. When a node stops rebalance, it results in the error message "Resetting rebalance status since it is not really running".
Rebalance cna also fail due to the timeout in
bulk_set_vbucket_state operation with
continuous view queries.
Microsoft Windows 7: when you create a bucket immediately after another bucket is deleted, Couchbase Server may timeout.
Issues: MB-6664
memcached hangs when aborting during swap rebalance operation and fails to restart ( exit 71 ).
Issues: MB-6592
Web Console
Command-line Tools
The cbbackup, cbrestore,
and cbtransfer command-line tools require the
zlib module for Python to have been
installed. If Python was installed from source, you must have
enabled zlib using the
--with-zlib option during the build process.
Issues: MB-7256
For more information, see 「バックアップとリストア」, 付録B Couchbase Serverのアンインストール.
Indexing and Querying
Development indexes will remain on disk after bucket deletion.
Issues: MB-6366
Accessing a recently created view (with other, existing active views) may return a error if the corresponding design document and view definition have not been replicated across the cluster. The error return will be returned in error of the view output detailing the missing design document. The workaround is to add views and design documents to your node or cluster after you have performed rebalance. For more information about resolving issues with Couchbase Views, see 付録D ビューのトラブルシューティング（技術的背景）.
Note also that stopping a rebalance operation on a cluster may take a long time if compaction and indexing operations are in progress on the cluster at the point of rebalance. Again, the workaround is to add views and index and query views after you have performed compaction or rebalance. For more information about rebalance, and considerations on when to rebalance, see 「クラスターの拡張と縮小（リバランス）」.
If a cluster is being rebalanced, and a node does not yet have
any active vBuckets, you will receive the error
"error":"no_active_vbuckets" when you query a
view via the REST API.
Issues: MB-6633
Indexing 11 design documents at once will significantly reduce Couchbase Server response times.
Issues: MB-6392
Cross Datacenter Replication (XDCR)
beam.smp memory usage grows to 2 GB when XDCR feature is enabled and rebalancing is in progress.
Issues: MB-6649
Very inconsistent statistics may occur with bi-directional XDCR when running with a moderate/low load.
Issues: MB-6598
Replication rat e may drop when the XDCR replication queue size becomes less than 500 items.
Issues: MB-6586
You may experience very slow replication rates (less than 100 items on average per second) with 2 unidirectional replications between 2 clusters.
Issues: MB-6643
Performance