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 Section 6.4, “Viewing Bucket and Cluster Statistics”.
Use the mutation log compactor sleep time from the configuration
Check each vbucket's bg queue to set the task sleep time
Only one access scanner should be scheduled at any time
Refactor add_with_meta test function
Update access scanner run counter when it is completed.
Requeue failed bgfetch requests for retry
Disable access scanner scheduling at a specific time
Reset checkpoint cursors after receiving backfill streams
Remove the mutation log if exists at the end of each test runs
expose TAP_FLAG_TAP_FIX_FLAG_BYTEORDER to python
return TMPFAIL for failed bgfetch instead of assert
Fixed iterate_ddocs return values
Replication stats on UI
Faster xdcr startup by using cached remote cluster info
Add logs to time replication stop
Send out email alerts asynchronously.
Don't send web alerts emails when they are disabled.
Added cancel bucket compaction button
Periodically update replica indexes.
Restart view compaction when getting shutdown errors.
Expose xdcr replications via tasks API
Maintain and collect XDCR vb stats
Added false/true options for reduce
REST API to alter set view update daemon parameters
REST API to update per ddoc updateMinChanges.
Don't shutdown bucket unless we're deleting it
Use optimized math for cache miss rate
Add compaction_daemon settings to config on upgrade.
More efficient index state computation
Allow sending web alerts via email.
Sort ddocs by id on ddocs endpoint
Inform user whether swap rebalance happens
Move email helpers from ns_mail_log to ns_mail.
Enabled emails for all alerts by default
Implemented replication cancellation endpoint
Fixed saving map/reduce functions into wrong views
Bump up default MAX_CONCURRENT_REPS_PER_DOC to 32
Started new REST api docs
Indexing and Querying
Fix too high memory consumption during indexing
Ignore index pausing of already paused partitions
More explicit error message when keys are too long
Delete index files on terminate after ddoc updated
Delete compaction file if index compactor dies
Delete index files on view group terminate
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.
Documents identified as Non-JSON stored within Couchbase Server may appear as binary, or text-encoded binary data within the UI.
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.
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
zlib using the
--with-zlib option during the build process.
Indexing and Querying
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 Appendix D, Troubleshooting Views (Technical Background).
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 Section 5.7, “Rebalancing”.