![ありがとうございました
そして、Couch [Tokyo] へ!
2014.1.21](https://image.slidesharecdn.com/couchbasemeetup20131212-140212084855-phpapp02/85/Couchbase-meetup20131212-look-back-in-2013-81-320.jpg)
Couchbase meetup20131212 [look back in 2013]
- 2. 自己紹介(とだこういち) • ここ２∼３年はSolr/lucneを使用した検索システムの 開発に従事（特許検索、地図検索など）していました • ６月にCouchbaseに気づき、たちまち fall in love • 現在、Couchbaseに関する技術支援・トレーニング 講師をしています • また、Couchbase 技術文献の翻訳(White Paper等) もしています
- 7. 2.0.1 （3月）
- 8. 2.0.1 Release Notes for Couchbase Server 2.0.1 GA (March 2013)¶ Couchbase Server 2.0.1 is first maintenance release for Couchbase Server 2.0. This release contains number of enhancements particularly for the rebalance, indexing and compaction operations. In addition, it also includes some critical bug fixes related to system timeouts and system stability. This includes: ! Couchbase Server 2.0.1は、 • Improves rebalance operation time for key-value use cases. Couchbase Server 2.0における最初のメンテナンスリリースです。 the • Improves coordination of index compaction and index building that occurs during rebalance operation. This helps significantly reduce the index file size growth during このリリースには、いくつかのパフォーマンス向上が含まれます。 rebalance. この中には、リバランス、インデキシング、コンパクション処理が • Changes to high and low water marks that provides more usable memory for users. 含まれます。 problems that were seen due to Erlang VM settings. • Fixes timeout 加えて、システムタイムアウトや、システムの安定性に関するいくつか • Fixes a critical indexing problem. A document that produced a runtime failure in one view had been unavailable to all other views within the same design document. の致命的なバクについてのバグフィックスがなされています。
- 9. 2.0.1 Release Notes for Couchbase Server 2.0.1 GA (March 2013)¶ Couchbase Server 2.0.1 is first maintenance release for Couchbase Server 2.0. This release contains number of enhancements particularly for the rebalance, indexing and compaction operations. In addition, it also includes some critical bug fixes related to system timeouts and system stability. This includes: ! • Improves rebalance operation time for key-value use cases. ! • Improves coordination of index compaction and index building that occurs during the rebalance operation. This helps significantly reduce the index file size growth during key-valueユースケースにおける、リバランス処理時間が改善しています。 rebalance. • Changes to high and low water marks that provides more usable memory for users. • Fixes timeout problems that were seen due to Erlang VM settings. • Fixes a critical indexing problem. A document that produced a runtime failure in one view had been unavailable to all other views within the same design document.
- 10. 2.0.1 Release Notes for Couchbase Server 2.0.1 GA (March 2013)¶ Couchbase Server 2.0.1 is first maintenance release for Couchbase Server 2.0. This release contains number of enhancements particularly for the rebalance, indexing and compaction operations. In addition, it also includes some critical bug fixes related to system timeouts and system stability. This includes: ! • Improves rebalance operation time for key-value use cases. • Improves coordination of index compaction and index building that occurs during the rebalance operation. This helps significantly reduce the index file size growth during rebalance. ! • Changes to high and low water marks that provides more usable memory for users. • Fixes timeout problems that were seen due to Erlang VM settings. リバランス処理中に発生した、インデックスのコンパクションと、インデックス生成の整合性が向 上しました。 • Fixes a critical indexing problem. A document that produced a runtime failure in one これは、リバランス中におけるインデックスファイルサイズの増加を著しく低減することに寄与し view had been unavailable to all other views within the same design document. ます。
- 11. 2.0.1 Release Notes for Couchbase Server 2.0.1 GA (March 2013)¶ Couchbase Server 2.0.1 is first maintenance release for Couchbase Server 2.0. This release contains number of enhancements particularly for the rebalance, indexing and compaction operations. In addition, it also includes some critical bug fixes related to system timeouts and system stability. This includes: ! • Improves rebalance operation time for key-value use cases. • Improves coordination of index compaction and index building that occurs during the rebalance operation. This helps significantly reduce the index file size growth during rebalance. • Changes to high and low water marks that provides more usable memory for users. ! • Fixes timeout problems that were seen due to Erlang VM settings. • Fixes a critical indexing problem. A document that produced a runtime failure in one ハイウォータマークと、ロウウォータマークを変更し、ユーザがより多くのメモリ領域 view had been unavailable to all other views within the same design document. を利用できるようにしました。
- 12. High Water Markは 2.0.1+ から85%でした Ejection and Working Set Managemen というわかりにくい所に記載がありました。
- 14. 2.0.1 Release Notes for Couchbase Server 2.0.1 GA (March 2013)¶ Couchbase Server 2.0.1 is first maintenance release for Couchbase Server 2.0. This release contains number of enhancements particularly for the rebalance, indexing and compaction operations. In addition, it also includes some critical bug fixes related to system timeouts and system stability. This includes: ! • Improves rebalance operation time for key-value use cases. • Improves coordination of index compaction and index building that occurs during the rebalance operation. This helps significantly reduce the index file size growth during rebalance. • Changes to high and low water marks that provides more usable memory for users. • Fixes timeout problems that were seen due to Erlang VM settings. • Fixes a critical indexing problem. A document that produced a runtime failure in one ! view had been unavailable to all other views within the same design document. Erlang VM設定をする必要のあった、タイムアウト問題を解決しました。
- 15. 2.0.1 Release Notes for Couchbase Server 2.0.1 GA (March 2013)¶ Couchbase Server 2.0.1 is first maintenance release for Couchbase Server 2.0. This release contains number of enhancements particularly for the rebalance, indexing and compaction operations. In addition, it also includes some critical bug fixes related to system timeouts and system stability. This includes: ! • Improves rebalance operation time for key-value use cases. ! • Improves coordination of index compaction and index building that occurs during the 同じdesign document内の、あるViewにおいてランタイム障害を引き起こしたドキュメ rebalance operation. This helps significantly reduce the index file size growth during rebalance. ントは、その他の全てのviewでも利用できなくなるという問題が発生していましたが、 • Changes to high and low water marks that provides この致命的なインデキシング問題を解決しました。 more usable memory for users. • Fixes timeout problems that were seen due to Erlang VM settings. • Fixes a critical indexing problem. A document that produced a runtime failure in one view had been unavailable to all other views within the same design document.
- 16. 2.0.1 Fixes in 2.0.1 • Installation and Upgrade ◦ We now provide a warning message on minimal system requirements for Couchbase Server. This appears on Linux in the terminal, and on Windows as a InstallShield screen. For more information about minimum platform requirements, see the section Preparation. Issues : MB-7482 • Cluster Operations ! ◦ The server had experienced timeouts during rebalance if views were being indexed or compacted at the Couchbase Serverの最小システム要件（を満たさない場合は）ワーニングメッセージを出力するよ same time. This resulted in the rebalance to fail. This has been fixed. Issues : MB-6595 うにしました。これはLinuxの場合はターミナルに表示されます。また、WindowsではInstallSheild ◦ In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding スクリーンに表示されます。詳細については「Preparation」セクションを参照。 2.0 nodes, the dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster references to be lost on the 2.0 nodes and would produce this error message "case_clause,error". This is now fixed. Issues : MB-7568 ◦ The server had experienced random timeouts possible due to lack of asynchronous I/O threads. This caused rebalance to fail. This has been fixed. Issues : MB-7182 • Command-line Tools ◦ There is a new setting available in cbepctl named mutation_mem_threshold. This is the amount of RAM that can be used on the server before a client begins receiving temporary out of memory errors. For more information, see Changing Setting for Out Of Memory Errors. Issues : MB-7540
- 17. 2.0.1 Fixes in 2.0.1 • Installation and Upgrade ◦ We now provide a warning message on minimal system requirements for Couchbase Server. This appears on Linux in the terminal, and on Windows as a InstallShield screen. For more information about minimum platform requirements, see the section Preparation. Issues : MB-7482 • Cluster Operations ◦ The server had experienced timeouts during rebalance if views were being indexed or compacted at the same time. This resulted in the rebalance to fail. This has been fixed. Issues : MB-6595 ◦ In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding 2.0 nodes, the dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster もしもリバランスと同時にviewがインデックス化されたか、コンパクションされた場合には、リバ references to be lost on the 2.0 nodes and would produce this error message "case_clause,error". This is now fixed. ランスがタイムアウトするという現象が起きていました。そしてこの場合、リバランスが失敗して Issues : MB-7568 ! いました。この問題を解決しました。 ◦ The server had experienced random timeouts possible due to lack of asynchronous I/O threads. This caused rebalance to fail. This has been fixed. Issues : MB-7182 • Command-line Tools ◦ There is a new setting available in cbepctl named mutation_mem_threshold. This is the amount of RAM that can be used on the server before a client begins receiving temporary out of memory errors. For more information, see Changing Setting for Out Of Memory Errors. Issues : MB-7540
- 18. 2.0.1 Fixes in 2.0.1 • Installation and Upgrade ◦ We now provide a warning message on minimal system requirements for Couchbase Server. This appears on Linux in the terminal, and on Windows as a InstallShield screen. For more information about minimum platform requirements, see the section Preparation. Issues : MB-7482 • Cluster Operations ◦ The server had experienced timeouts during rebalance if views were being indexed or compacted at the same time. This resulted in the rebalance to fail. This has been fixed. Issues : MB-6595 ◦ In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding 2.0 nodes, the dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster references to be lost on the 2.0 nodes and would produce this error message "case_clause,error". This is now fixed. Issues : MB-7568 ◦ The server had experienced random timeouts possible due to lack of asynchronous I/O threads. This caused rebalance to fail. This has been fixed. Issues : MB-7182 これまでは、1.8から2.0でのオンライン・アップグレードを、2.0ノードを追加することにより実 ! 行した場合、2.0ノード上の dynamic configuration fileは、消去されていましました。この結果 • Command-line Tools XDCRのリモートクラスタ参照は、この2.0ノードを見失い、"case_clause,error"を出力しました ◦ There is a new setting available in cbepctl named mutation_mem_threshold. This is the amount of RAM that can be used on the が、この問題を解決しました。 server before a client begins receiving temporary out of memory errors. For more information, see Changing Setting for Out Of Memory Errors. Issues : MB-7540
- 19. 2.0.1 Fixes in 2.0.1 • Installation and Upgrade ◦ We now provide a warning message on minimal system requirements for Couchbase Server. This appears on Linux in the terminal, and on Windows as a InstallShield screen. For more information about minimum platform requirements, see the section Preparation. Issues : MB-7482 • Cluster Operations ◦ The server had experienced timeouts during rebalance if views were being indexed or compacted at the same time. This resulted in the rebalance to fail. This has been fixed. Issues : MB-6595 ◦ In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding 2.0 nodes, the dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster references to be lost on the 2.0 nodes and would produce this error message "case_clause,error". This is now fixed. Issues : MB-7568 ◦ The server had experienced random timeouts possible due to lack of asynchronous I/O threads. This caused rebalance to fail. This has been fixed. Issues : MB-7182 ! • Command-line Tools ◦ There is a new setting available in cbepctl named mutation_mem_threshold. This is the amount of 非同期I/Oスレッドが欠乏すると、ランダムなタイムアウトが発生していました。この結果 、リバラ RAM that can be used on the server before a client begins receiving temporary out of memory errors. ンスが失敗することがありましたがこの問題を解決しました。Errors. For more information, see Changing Setting for Out Of Memory Issues : MB-7540
- 20. 2.0.1 Fixes in 2.0.1 • Installation and Upgrade ◦ We now provide a warning message on minimal system requirements for Couchbase Server. This appears on Linux in the terminal, and on Windows as a InstallShield screen. For more information about minimum platform requirements, see the section Preparation. Issues : MB-7482 • Cluster Operations ◦ The server had experienced timeouts during rebalance if views were being indexed or compacted at the same time. This resulted in the rebalance to fail. This has been fixed. Issues : MB-6595 ◦ In the past, if you were performing an online upgrade of a 1.8 cluster to 2.0 by adding 2.0 nodes, the dynamic configuration file on 2.0 nodes would be purged. This resulted in any XDCR remote cluster ! references to be lost on the 2.0 nodes and would produce this error message "case_clause,error". This is now fixed. cbepctlコマンドに、mutation_mem_thresholdという新しい設定が追加されました。これは、クライ Issues : MB-7568 アントが、テンポラリのアウト・オブ・メモリエラーを受け付けるよりも前にサーバ上で利用でき ◦ The server had experienced random timeouts possible due to lack of asynchronous I/O threads. This るRAMの容量です。詳細は、「Changing fixed. for Out Of Memory Errors」参照のこと。 caused rebalance to fail. This has been Setting Issues : MB-7182 • Command-line Tools ◦ There is a new setting available in cbepctl named mutation_mem_threshold. This is the amount of RAM that can be used on the server before a client begins receiving temporary out of memory errors. For more information, see Changing Setting for Out Of Memory Errors. Issues : MB-7540
- 21. 2.0.1 • Indexing and Querying ◦ In past releases of Couchbase Server 2.0, if you had a map function that failed to index, other functions in the same design document would also fail. This has been fixed. Issues : MB-6895 ! ◦ During rebalance, index files were growing to an unnecessarily large size. This has been fixed. Issues : MB-6799 ! ◦ There is a new REST API call which can be used if you experience a slow rebalance while indexing and compaction are in progress. For more information, see Adjusting Rebalance during の他の（Map・Reduce）関数はすべて失敗していましたが、この問題が解決されました。 Compaction. Issues : MB-7843 これまでは、あるMap関数が、インデックスの生成に失敗した場合、同じデザインドキュメント中 • Cross Datacenter Replication (XDCR) ◦ Stats for XDCR had erroneously omitted the time taken to commit items and had also displayed the incorrect number of documents/mutations checked and replicated. This is fixed. Issues : MB-7275 ◦ When you create a replication between two clusters, you may see two error messages: “Failed to grab remote bucket info, vbucket” and “Error replicating vbucket X”. Nonetheless, replication will still start and then function as expected, but the error messages may appear for some time in the Web Console. This has been fixed. Issues : MB-7786, MB-7457
- 22. 2.0.1 • Indexing and Querying ◦ In past releases of Couchbase Server 2.0, if you had a map function that failed to index, other functions in the same design document would also fail. This has been fixed. Issues : MB-6895 ◦ During rebalance, index files were growing to an unnecessarily large size. This has been fixed. Issues : MB-6799 ◦ There is a new REST API call which can be used if you experience a slow rebalance while indexing and compaction are in progress. For more information, see Adjusting Rebalance during Compaction. Issues : MB-7843 ! ! リバランスの間、インデックスファイルは、不必要に大きなサイズまで増加する問題がありました • Cross Datacenter Replication (XDCR) が、この問題が解決されました。 ◦ Stats for XDCR had erroneously omitted the time taken to commit items and had also displayed the incorrect number of documents/mutations checked and replicated. This is fixed. Issues : MB-7275 ◦ When you create a replication between two clusters, you may see two error messages: “Failed to grab remote bucket info, vbucket” and “Error replicating vbucket X”. Nonetheless, replication will still start and then function as expected, but the error messages may appear for some time in the Web Console. This has been fixed. Issues : MB-7786, MB-7457
- 23. 2.0.1 • Indexing and Querying ◦ In past releases of Couchbase Server 2.0, if you had a map function that failed to index, other functions in the same design document would also fail. This has been fixed. Issues : MB-6895 ◦ During rebalance, index files were growing to an unnecessarily large size. This has been fixed. Issues : MB-6799 ◦ There is a new REST API call which can be used if you experience a slow rebalance while indexing and compaction are in progress. For more information, see Adjusting Rebalance during Compaction. Issues : MB-7843 !• Cross Datacenter Replication (XDCR) インデキシングとコンパクションが進行している間にリバランスを行った場合に、処理が遅くなる ◦ Stats for XDCR had erroneously omitted the time taken to commit items and had also displayed the incorrect number of documents/mutations checked and replicated. This is fixed. 場合がありました。このリバランスのパフォーマンス低下を改善する新しいREST API呼び出しが提 Issues : MB-7275 供されます。詳細は「Adjusting Rebalance during Compaction」を参照。 ◦ When you create a replication between two clusters, you may see two error messages: “Failed to grab remote bucket info, vbucket” and “Error replicating vbucket X”. Nonetheless, replication will still start and then function as expected, but the error messages may appear for some time in the Web Console. This has been fixed. Issues : MB-7786, MB-7457
- 24. 2.0.1 • Indexing and Querying ◦ In past releases of Couchbase Server 2.0, if you had a map function that failed to index, other functions in the same design document would also fail. This has been fixed. Issues : MB-6895 ◦ During rebalance, index files were growing to an unnecessarily large size. This has been fixed. Issues : MB-6799 ◦ There is a new REST API call which can be used if you experience a slow rebalance while indexing and compaction are in progress. For more information, see Adjusting Rebalance during Compaction. Issues : MB-7843 • Cross Datacenter Replication (XDCR) ◦ Stats for XDCR had erroneously omitted the time taken to commit items and had also displayed the incorrect number of documents/mutations checked and replicated. This is fixed. Issues : MB-7275 ◦ When you create a replication between two clusters, you may see two error messages: “Failed to grab remote bucket info, vbucket” and “Error replicating vbucket X”. Nonetheless, replication will コミットに時間がかかったitemについて、XDCRのための統計情報が、誤って省略されていまし still start and then function as expected, but the error messages may appear for some time in the Web Console. This has been fixed. た。このためチェックされ、レプリケートされた、ドキュメント数/変更数について正しくない件数 Issues : MB-7786, MB-7457 ! が表示されていました。これを修正しました。
- 25. 2.0.1 • Indexing and Querying ◦ In past releases of Couchbase Server 2.0, if you had a map function that failed to index, other functions in the same design document would also fail. This has been fixed. Issues : MB-6895 ◦ During rebalance, index files were growing to an unnecessarily large size. This has been fixed. Issues : MB-6799 ◦ There is a new REST API call which can be used if you experience a slow rebalance while indexing and compaction are in progress. For more information, see Adjusting Rebalance during ! Compaction. クラスタ間のレプリケーションを生成した時、2つのエラーメッセージ( Failed to grab remote Issues : MB-7843 bucket info, vbucket , Error replicating vbucket X )が表示されていました。この表示がされて • Cross Datacenter Replication (XDCR) いても、レプリケーションは問題なく開始されます。しかしエラーメッセージは、Webコンソール ◦ Stats for XDCR had erroneously omitted the time taken to commit items and had also displayed the 上に時々表示されるといった状態になっていましたが、この問題を修正しました。 incorrect number of documents/mutations checked and replicated. This is fixed. Issues : MB-7275 ◦ When you create a replication between two clusters, you may see two error messages: “Failed to grab remote bucket info, vbucket” and “Error replicating vbucket X”. Nonetheless, replication will still start and then function as expected, but the error messages may appear for some time in the Web Console. This has been fixed. Issues : MB-7786, MB-7457
- 26. 2.1.0（６月）
- 27. 2.1.0 Release Notes for Couchbase Server 2.1.0 GA (June 2013)¶ Couchbase Server 2.1.0 is the first minor release for Couchbase Server 2.0 and includes several optimizations, new features and important bug fixes. The major enhancements available in Couchbase Server 2.1.0 include: ! • Improved disk read and write performance with new multiCouchbase Server persistence engine. With the newly designed threaded 2.1.0は、Couchbase Server 2.0のマイナーリリースであり、この版では、いくつ かの最適化、新規機能、そして重要なバグフィックスが含まれます。Couchbase Server 2.1.0で可 persistence engine, users can configure the multiple read能になった主要な改善点は以下。 write workers on a per Bucket basis. See Disk Storage.
- 28. 2.1.0 Release Notes for Couchbase Server 2.1.0 GA (June 2013)¶ Couchbase Server 2.1.0 is the first minor release for Couchbase ! Server 2.0 and includes several optimizations, new features and マルチスレッド化された永続化エンジンにより、ディスクへの読込み、書込みのパフォーマンスが important bug fixes. 改善されました。新しくデザインされたエンジンを使って、ユーザは、バケット単位で、multiple The major enhancements available in Storage」参照。 read-write workerを設定できるようになりました。「Disk Couchbase Server 2.1.0 include: • Improved disk read and write performance with new multithreaded persistence engine. With the newly designed persistence engine, users can configure the multiple readwrite workers on a per Bucket basis. See Disk Storage.
- 29. Disk周りが,マルチスレッド化
- 30. 2.1.0 • Optimistic Replication mode for XDCR to optimistically replicate mutations to the target cluster. More information can be found here: ‘Optimistic Replication’ in XDCR • More XDCR Statistics to monitor performance and behavior of XDCR. See Monitoring Outgoing XDCR. XDCRへの楽観的レプリケーションモード（ターゲットクラスタに対する楽観的なレプリケート • mutation）を提供します.詳細は「xdcrOptimisticReplicationThreshold」を参照。 Support for hostnames when setting up Couchbase Server. See Using Hostnames with Couchbase Server. • Rebalance progress indicator to provide more visibility into rebalance operation. See Monitoring a Rebalance. • Ability to generate a health report with cbhealthchecker, now included as part of the Couchbase Server install. See cbhealthchecker Tool. • Importing and exporting of CSV files with Couchbase using cbtransfer. See cbtransfer Tool. • Server-side replica-read API. Couchbase Developer Guide, Replica
- 31. 2.1.0 • Optimistic Replication mode for XDCR to optimistically replicate mutations to the target cluster. More information can be found here: ‘Optimistic Replication’ in XDCR • More XDCR Statistics to monitor performance and behavior of XDCR. See Monitoring Outgoing XDCR. • Support for hostnames when setting up Couchbase Server. See Using Hostnames with Couchbase Server. XDCRの統計情報が追加され、XDCRのパフォーマンスや挙動をモニタできるようになりました。 • 「Monitoring Outgoing XDCR」を参照。 to provide more visibility into rebalance Rebalance progress indicator operation. See Monitoring a Rebalance. • Ability to generate a health report with cbhealthchecker, now included as part of the Couchbase Server install. See cbhealthchecker Tool. • Importing and exporting of CSV files with Couchbase using cbtransfer. See cbtransfer Tool. • Server-side replica-read API. Couchbase Developer Guide, Replica
- 32. 2.1.0 • Optimistic Replication mode for XDCR to optimistically replicate mutations to the target cluster. More information can be found here: ‘Optimistic Replication’ in XDCR • More XDCR Statistics to monitor performance and behavior of XDCR. See Monitoring Outgoing XDCR. • Support for hostnames when setting up Couchbase Server. See Using Hostnames with Couchbase Server. • Rebalance progress indicator to provide more visibility into rebalance operation. See Monitoring a Rebalance. Couchbase Serverの設定時に、hostnameが設定できるようになりました。「Using Hostnames • with Couchbase Server」を参照。 report with cbhealthchecker, now Ability to generate a health included as part of the Couchbase Server install. See cbhealthchecker Tool. • Importing and exporting of CSV files with Couchbase using cbtransfer. See cbtransfer Tool. • Server-side replica-read API. Couchbase Developer Guide, Replica
- 33. 2.1.0 • Optimistic Replication mode for XDCR to optimistically replicate mutations to the target cluster. More information can be found here: ‘Optimistic Replication’ in XDCR • More XDCR Statistics to monitor performance and behavior of XDCR. See Monitoring Outgoing XDCR. • Support for hostnames when setting up Couchbase Server. See Using Hostnames with Couchbase Server. • Rebalance progress indicator to provide more visibility into rebalance operation. See Monitoring a Rebalance. • Ability to generate a health report with cbhealthchecker, now included as part of the Couchbase Server install. See cbhealthchecker リバランスのプログレス表示が、リバランス処理をより視覚的に表示するようになりました。「See Tool. Monitoring a Rebalance」を参照。 • Importing and exporting of CSV files with Couchbase using cbtransfer. See cbtransfer Tool. • Server-side replica-read API. Couchbase Developer Guide, Replica
- 34. 2.1.0 • Optimistic Replication mode for XDCR to optimistically replicate mutations to the target cluster. More information can be found here: ‘Optimistic Replication’ in XDCR • More XDCR Statistics to monitor performance and behavior of XDCR. See Monitoring Outgoing XDCR. • Support for hostnames when setting up Couchbase Server. See Using Hostnames with Couchbase Server. • Rebalance progress indicator to provide more visibility into rebalance operation. See Monitoring a Rebalance. • Ability to generate a health report with cbhealthchecker, now included as part of the Couchbase Server install. See cbhealthchecker Tool. • Importing and exporting of CSV files with Couchbase using cbhealthcheckerにより、ヘルス・レポートを生成するようになりました。また、これは、Couchbase cbtransfer. See cbtransfer Tool. Serverのインストールパッケージに含まれるようになりました。「cbhealthchecker Tool」を参照。 • Server-side replica-read API. Couchbase Developer Guide, Replica
- 35. 2.1.0 • Optimistic Replication mode for XDCR to optimistically replicate mutations to the target cluster. More information can be found here: ‘Optimistic Replication’ in XDCR • More XDCR Statistics to monitor performance and behavior of XDCR. See Monitoring Outgoing XDCR. • Support for hostnames when setting up Couchbase Server. See Using Hostnames with Couchbase Server. • Rebalance progress indicator to provide more visibility into rebalance operation. See Monitoring a Rebalance. cbtransferコマンドにより、CSVファイルによる、インポート・エクスポートができるようになりま • した。「cbtransfer Tool」を参照。 report with cbhealthchecker, now Ability to generate a health included as part of the Couchbase Server install. See cbhealthchecker Tool. • Importing and exporting of CSV files with Couchbase using cbtransfer. See cbtransfer Tool. • Server-side replica-read API. Couchbase Developer Guide, Replica
- 36. 2.1.0 • Optimistic Replication mode for XDCR to optimistically replicate mutations to the target cluster. More information can be found here: ‘Optimistic Replication’ in XDCR • More XDCR Statistics to monitor performance and behavior of XDCR. See Monitoring Outgoing XDCR. • Support for hostnames when setting up Couchbase Server. See Using Hostnames with Couchbase Server. • Rebalance progress indicator to provide more visibility into rebalance operation. See Monitoring a Rebalance. • Ability to generate a health report with cbhealthchecker, now included as part of the Couchbase Server install. See cbhealthchecker サーバサイドのレプリカ読込APIが追加されました。「Couchbase Developer Guide, Replica Tool. Read」参照。 • Importing and exporting of CSV files with Couchbase using cbtransfer. See cbtransfer Tool. • Server-side replica-read API. Couchbase Developer Guide, Replica
- 37. レプリカ読み込み 8.4. Replica Read As of Couchbase Server 2.1.0, we have a binary protocol to retrieve replicated data for a given key. The command is similar to the existing binary get command, however it returns data from a vBucket that is in a replica state as opposed to an active state. In case of node failure you can have an application retry the server and wait until replicated data is available on another node. Couchbase Server takes 30 seconds to detect a node has failed, automatically failover the node, and then elevate replicated data to an active state on another node. If you do not have automatic failover enabled, it may take even longer for human intervention and manual failover. ! Although clients can wait and retry a read, you may have a scenario where you cannot Couchbaseseconds to detect node failure, perform failover and activate replicated data. wait 30 Server 2.1.0では、レプリケートデータを読み出すためのバイナリプロトコルが提供されま For instance if you a SLA that requires you to get data within 30 seconds of a request す。このコマンドは、getコマンドに類似していますが、アクティブステートではなく、レプリカステー or less, you may need replica read functionality. In this case you can use replica read トのデータがvBucketから返却されます。ノード障害では、アプリケーションはリトライにより、レプ at the binary protocol level or as it is available in Couchbase SDKs. For more リカデータが他のノードで利用可能になるまで待ちます。 ! information about node failure and failover, see Couchbase Server Manual, Failing ! Over Nodes. Couchbase Serverは、ノードに障害が起きたことを判断するのに、30秒かかります。自動的にノー If you create your own Couchbase client, you can also create a wrapper on this ドのフェイルオーバができ、そして、他ノード上にあるレプリカデータは、アクティブステートに昇格 protocol to provide replica reads. することになります。もしも、あなたが、オートフェイルオーバを有効にしていなければ、手動のフェ The request is identical to a get request with the exception of the Opcode of 0x83: イルオーバをすることになり、さらに長時間を要します。
- 38. レプリカ読み込み 8.4. Replica Read ! ! As of Couchbase Server 2.1.0, we have a binary protocol to retrieve replicated data for a given key. The command is similar to the existing binary get command, however it しかし、あなたにはシナリオがあり、30秒も待ってノード障害が判断され、フェールオーバを実行 returns data from a vBucket that is in a replica state as opposed to an active state. し、レプリカデータがアクティベートするまでの間、待てないかもしれない。例えば、もしもSLAが設 In case of node failure you can have an application retry the server and wait until 定されており、30秒以内に、データを取得することが求められている場合、レプリカ読み込みを使用 replicated data is available on another node. Couchbase Server takes 30 seconds to する必要があるかもしれません。このケースでは、あなたは、レプリカ読み込みをバイナリプロトコル detect a node has failed, automatically failover the node, and then elevate replicated レベルで使用することが可能であり、Couchbaseyou do not have automatic failover enabled, data to an active state on another node. If SDKで使用することもできます。 it may take even longer for human intervention and manual failover. Although clients can wait and retry a read, you may have a scenario where you cannot wait 30 seconds to detect node failure, perform failover and activate replicated data. For instance if you a SLA that requires you to get data within 30 seconds of a request or less, you may need replica read functionality. In this case you can use replica read at the binary protocol level or as it is available in Couchbase SDKs. For more information about node failure and failover, see Couchbase Server Manual, Failing Over Nodes. If you create your own Couchbase client, you can also create a wrapper on this protocol to provide replica reads. The request is identical to a get request with the exception of the Opcode of 0x83:
- 39. レプリカ読み込み A.2. Release Notes for Couchbase Client Library Java 1.1.8 GA (9 July 2013)より抜粋
- 40. 2.1.0 Additional behavior changes in 2.1.0 include: • Backup, Restore and Transfer tool to optionally transfer data or design documents only. The default is to transfer both data and design documents. See cbbackup Tool, cbrestore Tool, cbtransfer Tool • Improved cluster manager stability via separate process for cluster バックアップ、レストア、転送ツールは、オプションで、データ転送か、デザインドキュメントかの manager. See Underlying Server Processes. どちらかを選択して行うことができるようになりました。デフォルトでは、両方のデータを転送しま • す。「cbbackup Tool」,tools updated 「cbtransfer Tool」を参照。 nodes, buckets, Command Line 「cbrestore Tool」, so you can manage clusters and XDCR. See couchbase-cli Tool • Several new and updated statistics for XDCR on the admin Console and via the REST API. For more information, see Monitoring Incoming XDCR, Monitoring Outgoing XDCR, and Getting XDCR Stats via REST.
- 41. 2.1.0 Additional behavior changes in 2.1.0 include: • Backup, Restore and Transfer tool to optionally transfer data or design documents only. The default is to transfer both data and design documents. See cbbackup Tool, cbrestore Tool, cbtransfer Tool • Improved cluster manager stability via separate process for cluster manager. See Underlying Server Processes. • Command Line tools updated so you can manage nodes, buckets, clusters and XDCR. See couchbase-cli Tool 改善されたクラスタマネージャは、クラスタマネジャ専用にプロセスを分離することにより、安定性 • が増しています。「See Underlying Server Processes」を参照。 on the admin Console and Several new and updated statistics for XDCR via the REST API. For more information, see Monitoring Incoming XDCR, Monitoring Outgoing XDCR, and Getting XDCR Stats via REST.
- 42. 2.1.0 Additional behavior changes in 2.1.0 include: • Backup, Restore and Transfer tool to optionally transfer data or design documents only. The default is to transfer both data and design documents. See cbbackup Tool, cbrestore Tool, cbtransfer Tool • Improved cluster manager stability via separate process for cluster manager. See Underlying Server Processes. • Command Line tools updated so you can manage nodes, buckets, clusters and XDCR. See couchbase-cli Tool • Several new and updated statistics for XDCR on the admin Console and via the REST API. For more information, see Monitoring Incoming コマンドラインツールが更新されました。このため、ノード、バケット、クラスタ、XDCRの管理が XDCR, Monitoring Outgoing XDCR, and Getting XDCR Stats via REST. できるようになりました。「couchbase-cli Tool」参照。
- 43. 2.1.0 Additional behavior changes in 2.1.0 include: • Backup, Restore and Transfer tool to optionally transfer data or design documents only. The default is to transfer both data and design documents. See cbbackup Tool, cbrestore Tool, cbtransfer Tool • Improved cluster manager stability via separate process for cluster いくつかのXDCRの統計情報が追加されたことにより、（管理コンソールでも）REST APIでもこの統 manager. See Underlying Server Processes. 計情報が参照できるようになりました。「Monitoring Incoming XDCR」,「Monitoring Outgoing • XDCR」, 「Getting XDCR Statsupdated so you can manage nodes, buckets, Command Line tools via REST」を参照。 clusters and XDCR. See couchbase-cli Tool • Several new and updated statistics for XDCR on the admin Console and via the REST API. For more information, see Monitoring Incoming XDCR, Monitoring Outgoing XDCR, and Getting XDCR Stats via REST.
- 44. 2.1.0 Fixes in 2.1.0 • Installation and Upgrade ◦ In the past Couchbase Server 2.0.0 upgrade installers on Linux did not replace the file2.beam with the latest version. This will cause indexing and querying to fail. This has been fixed. Issues : MB-7770 ◦ The Windows installer for Windows 32-bit and 64-bit now prompts これまでは、Linux環境でのCouchbase Server 2.0.0 のアップグレードインストーラは、file2.beam you to set the MaxUserPort registry setting. This will increase the ファイルを差し替えることをしませんでした(with the latest version)。これは、インデキシングとクエ number of ephemeral ports available to applications on Windows, as リが失敗する原因となっていましたが、この問題を解決しました。 documented in Microsoft Knowledge Base Article 196271. The installer also warns you that a reboot is necessary for this change to take effect. If this registry key is not set, it may lead to port exhaustion leading to various problems, see as MB-8321. For installer instructions, see Microsoft Windows Installation. Issues : MB-8321
- 45. 2.1.0 Windowsのインストーラ(32-bit,64-bit)は、MaxUserPortレジストリの設定を促すようになりました。 Fixes in 2.1.0 これはWindows上のアプリケーションが利用可能なエフェメラルポート(一時的な通信のために自由 • Installation and Upgrade に利用できるポート)の数を増加させることができます（Microsoft Knowledge Base Article 196271）。インストーラは、この変更を有効にするためリブートが必要であると、ワーニングを出力 ◦ In the past Couchbase Server 2.0.0 upgrade installers on Linux did します。もしも、このレジストリ・キーがセットされていない場合は、ポートを使い果たし、様々な not replace the file2.beam with the latest version. This will cause 問題を引き起こします(MB-8321参照)。インストーラの使用に関しては「Microsoft Windows indexing and querying to fail. This has been fixed. Installation」参照。 Issues : MB-7770 ◦ The Windows installer for Windows 32-bit and 64-bit now prompts you to set the MaxUserPort registry setting. This will increase the number of ephemeral ports available to applications on Windows, as documented in Microsoft Knowledge Base Article 196271. The installer also warns you that a reboot is necessary for this change to take effect. If this registry key is not set, it may lead to port exhaustion leading to various problems, see as MB-8321. For installer instructions, see Microsoft Windows Installation. Issues : MB-8321
- 46. 2.1.0 Fixes in 2.1.0 • Cluster Operations ◦ Previously, there was only one process that was responsible for monitoring and managing all the other underlying server processes. This includes Moxi and memcached, and also statistics gathering. Now there are two processes. One is responsible for just Moxi/Memcached and the other is responsible for monitoring all other processes. This should help prevent the max_restart_intensity seen when timeouts start and temporarily disrupted the server. The most noticeable change you see with this fix is that there are now two beam.smp processes running on Linux and two erl.exe running on Windows. For more details, see Underlying Server Processes. これまでは、全てのプロセスのモニタリングと管理に責任を持つのは、唯一のプロセスでした。これ Issues : MB-8376 にはMoxiや、memcachedや、統計情報の収集も含まれていました。これを2つのプロセスに分離しま した。1つは、Moxi/Memcachedにのみ責任を持つようにし、もう1つは、その他のプロセスのモニタ リングに責任を持つように構成しました。このことは、max_restart_intensity(最大リスタート数)に到 達することを防止することに寄与します。最も大きな変更は、Linux上では2つのbeam.smpプロセス の実行と、Windows上では2つのerl.exeの実行をするようになったことです。詳細は「Underlying Server Processes」を参照。
- 47. Fixes in 2.1.0 2.1.0 • Command-line Tools ◦ For earlier versions of Couchbase Server, some internal server directories were accessible all users, which was a security issue. This is now fixed. The fix now means that you should have root privileges when you run cbcollect_info because this tool needs this access level to collect all the information it needs to collect about the server. For more information about cbcollect_info, see cbcollect_info Tool. ◦ One XDCR REST API endpoint had a typo which is now fixed. The old Couchbase Serverの古いバージョンのために、いくつかの内部サーバディレクトリが全てのユーザに endpoint was /controller/cancelXCDR/:xid. The new, correct アクセス可能でした。これはセキュリティ上の問題となっておりました。今回これを修正しました。 endpoint is /controller/cancelXDCR/:xid. See Deleting XDCR 今後は、root権限が無ければ、cbcollect_infoツールを実行できないことを意味しています（なぜなら Replications. ば、このツールは、サーバについての情報を収集するアクセスレベルが必要になるためです）。 Issues : MB-8347 cbcollect_infoの詳細は、「cbcollect_info Tool」参照。 ◦ In the past when you used cbworkloadgen you see this error ImportError: No module named _sqlite3. This has been fixed. Issues : MB-8153
- 48. Fixes in 2.1.0 2.1.0 • Command-line Tools ◦ For earlier versions of Couchbase Server, some internal server directories were accessible all users, which was a security issue. This is now fixed. The fix now means that you should have root privileges when 一部のXDCR REST APIのエンドポイントに、ミススペルがあり、これを修正しました。古いエンド you run cbcollect_info because this tool needs this access level to ポイントは、/controller/cancelXCDR/:xidでしたが、新しくは /controller/cancelXDCR/:xid に修正さ collect all the information it needs れます。「Deleting XDCR Replications」参照。 to collect about the server. For more information about cbcollect_info, see cbcollect_info Tool. ◦ One XDCR REST API endpoint had a typo which is now fixed. The old endpoint was /controller/cancelXCDR/:xid. The new, correct endpoint is /controller/cancelXDCR/:xid. See Deleting XDCR Replications. Issues : MB-8347 ◦ In the past when you used cbworkloadgen you see this error ImportError: No module named _sqlite3. This has been fixed. Issues : MB-8153
- 49. Fixes in 2.1.0 2.1.0 • Command-line Tools ◦ For earlier versions of Couchbase Server, some internal server directories were accessible all users, which was a security issue. This is now fixed. The fix now means that you should have root privileges when you run cbcollect_info because this tool needs this access level to collect all the information it needs to collect about the server. For more information about cbcollect_info, see cbcollect_info Tool. ◦ One XDCR REST API endpoint had a typo which is now fixed. The old endpoint was /controller/cancelXCDR/:xid. The new, correct これまでは、cbworkloadgenを使用する時には、「ImportError: No See Deleting_sqlite3」と endpoint is /controller/cancelXDCR/:xid. module named XDCR いうエラーが出力されていましたが、これを修正しました。 Replications. Issues : MB-8347 ◦ In the past when you used cbworkloadgen you see this error ImportError: No module named _sqlite3. This has been fixed. Issues : MB-8153
- 50. Fixes in 2.1.0 2.1.0 • Indexing and Querying ◦ In the past too many simultaneous views requests could overwhelm a node. You can now limit the number of simultaneous requests a node can receive. For more information, see REST API, see Limiting Simultaneous Node Requests. Issues : MB-8199 これまでは、viewリクエストが同時に大量に発生した場合、ノード全体が圧倒されてしまう可能性が ありました。今後は、ノード当たりの同時リクエスト受付数を制限することができるようになりまし た。「REST API」, 「Limiting Simultaneous Node Requests」を参照。
- 53. 2.1.1（７月）
- 54. 2.1.1 Release Notes for Couchbase Server 2.1.1 GA (July 2013)¶ Couchbase Server 2.1.1 is first maintenance release for Couchbase Server 2.1. This release includes some major bug fixes and enhancements: New Edition in 2.1.1 The Enterprise 2.1.1 は、Couchbase ServerServer is now available on Mac OS X. See Couchbase Server Edition of Couchbase 2.1の最初のメンテナンスリリースです。このリリースで Couchbase, Downloads. は、いくつかの主要なバグフィックスと、機能改善が含まれます。 Fixes in 2.1.1 • Database Operations ◦ There was an underlying Windows Management Instrumentation issue in wmi_port.cpp which caused memory leaks. This has been fixed. Issues : MB-8674 ◦ The 2.1 version of the server exposes fewer server stats than it did in earlier versions. The five stats that have been removed are key_data_age, key_last_modification_time, paged_out _time, ep_too_young and ep_too_old. Issues : MB-8539
- 55. 2.1.1 Release Notes for Couchbase Server 2.1.1 GA (July 2013)¶ Couchbase Server 2.1.1 is first maintenance release for Couchbase Server 2.1. This release includes some major bug fixes and enhancements: New Edition in 2.1.1 The Enterprise Edition of Couchbase Server is now available on Mac OS X. See Couchbase, Downloads. Fixes in 2.1.1 • Database Operations (2.1系列の)Enterprise EditionがMac OS Xで利用可能になりました。ダウンロードページを参照。 ◦ There was an underlying Windows Management Instrumentation issue in wmi_port.cpp which caused memory leaks. This has been fixed. Issues : MB-8674 ◦ The 2.1 version of the server exposes fewer server stats than it did in earlier versions. The five stats that have been removed are key_data_age, key_last_modification_time, paged_out _time, ep_too_young and ep_too_old. Issues : MB-8539
- 56. 2.1.1 Release Notes for Couchbase Server 2.1.1 GA (July 2013)¶ Couchbase Server 2.1.1 is first maintenance release for Couchbase Server 2.1. This release includes some major bug fixes and enhancements: New Edition in 2.1.1 The Enterprise Edition of Couchbase Server is now available on Mac OS X. See Windows Management Instrumentationに関して、wmi_port.cppに起因したメモリーリーク問題が発生し Couchbase, Downloads. ていましたが、これを解決しました。 Fixes in 2.1.1 • Database Operations ◦ There was an underlying Windows Management Instrumentation issue in wmi_port.cpp which caused memory leaks. This has been fixed. Issues : MB-8674 ◦ The 2.1 version of the server exposes fewer server stats than it did in earlier versions. The five stats that have been removed are key_data_age, key_last_modification_time, paged_out _time, ep_too_young and ep_too_old. Issues : MB-8539
- 57. 2.1.1 Release Notes for Couchbase Server 2.1.1 GA (July 2013)¶ Couchbase Server 2.1.1 is first maintenance release for Couchbase Server 2.1. This release includes some major bug fixes and enhancements: New Edition in 2.1.1 The Enterprise Edition of Couchbase Server is now available on Mac OS X. See Couchbase, Downloads. Fixes in 2.1.1 • Database Operations 2.1バージョンは、それ以前のバージョンよりも、サーバステータスが削減されました。削除された5つ ◦ There was an underlying Windows Management Instrumentation issue in のステータスは、key_data_age, key_last_modification_time, paged_out _time, ep_too_young wmi_port.cpp which caused memory leaks. This has been fixed. and ep_too_oldです。 Issues : MB-8674 ◦ The 2.1 version of the server exposes fewer server stats than it did in earlier versions. The five stats that have been removed are key_data_age, key_last_modification_time, paged_out _time, ep_too_young and ep_too_old. Issues : MB-8539
- 58. 2.1.1 Fixes in 2.1.1 • Cluster Operations ◦ The rebalance speed for small datasets has been significantly improved. This includes time to rebalance empty buckets and buckets containing tens of thousands of items. Issues : MB-8521 ◦ In Couchbase 2.1.0 if you tried to assign a hostname to a node when you join the node to a cluster, it will be reset. The 少ないデータセットにおけるリバランスのスピードが著しく改善しました。これには、空のバケット や、数万個程度のitemしか含まないバケットのリバランスが含まれます。 hostname will not be saved for the node and will not be used by the cluster to identify the node. This has been fixed. For more information about managing hostnames, see Using Hostnames with Couchbase Server. Issues : MB-8545 !
- 59. 2.1.1 Fixes in 2.1.1 • Cluster Operations Couchbase 2.1.0 では、クラスタにノードを追加する際、hostnameをノードに対してアサインするこ とを試みた場合、リセットされてしまいました。hostnameは、ノードに保存されず、ノードを識別す ◦ The rebalance speed for small datasets has been significantly improved. This includes time to rebalance empty buckets and るために、クラスタにより利用されることもありませんでした。この問題を解決しました。「 Using buckets containing tens of thousands of items. Hostnames with Couchbase Server」参照。 Issues : MB-8521 ! ◦ In Couchbase 2.1.0 if you tried to assign a hostname to a node when you join the node to a cluster, it will be reset. The hostname will not be saved for the node and will not be used by the cluster to identify the node. This has been fixed. For more information about managing hostnames, see Using Hostnames with Couchbase Server. Issues : MB-8545
- 60. 2.2.0（９月）
- 61. 2.2.0 Release Notes for Couchbase Server 2.2 GA (September 2013)¶ Couchbase Server 2.2 is our minor update release for Couchbase Server 2.0. This includes some major enhancements, new features and important bug fixes. Also with this we have extended our platform support for Windows 2012 and provide separate packages for Ubuntu 12.04 and CentOS 6. Couchbase Server 2.2 は、Couchbase Server 2.0のマイナーバージョンアップです。これは、いくつかの 主要な改良、新機能、及びバグフィックスが含まれます。また、2.2より、プラットフォームサポートに Windows 2012を加え、Ubuntu 12.04とCentOS 6向けに専用のパッケージを用意しました。
- 62. 2.2.0 The major enhancements available in Couchbase Server 2.2 include: • XDCR performance optimization through new mode of replication which utilizes highly efficient memcached protocol on the destination cluster for replicating changes. See Behavior and Limitations. • Disk storage optimization through new metadata purge settings for permanently purge metadata on deleted items. See Disk XDCRのパフォーマンスが最適化されました。新しく設定されたレプリケーションモードにより、レプリ ケーション先のクラスタへのレプリケーションの変更のために、非常に効率の良いmemcachedプロトコ Storage. ルを使用できるようになりました。 user to Couchbase Server. This user will • New read-only admin have access to Couchbase Server and its Admin UI, tools and REST APIs but only in read-only mode. See Account Management. • New addition to our toolset CBRecovery tool that provides additional durability from remote cluster. See CLI Tools.
- 64. Couchbase Plug-in for Elasticsearch 1.2.0 Release Notes for Couchbase Plug-in for Elasticsearch 1.2.0 GA (October 2013)¶ ! This release adds compatibility with Elasticsearch 0.90.5. This release is compatible with Couchbase Server 2.2, and it is backward compatible with earlier 2.x releases. !
- 65. 2.2.0 The major enhancements available in Couchbase Server 2.2 include: • XDCR performance optimization through new mode of replication which utilizes highly efficient memcached protocol on the destination cluster for replicating changes. See Behavior and Limitations. • Disk storage optimization through new metadata purge settings for permanently purge metadata on deleted items. See Disk Storage. • New read-only admin user to Couchbase Server. This user will have access to Couchbase Server and its Admin UI, tools and ディスクストレージが最適化されました。新しいメタデータ除去設定により、削除されたアイテムについ REST APIs but only in read-only mode. See Account て、恒久的にメタデータを除去することが可能になりました。 Management. • New addition to our toolset CBRecovery tool that provides additional durability from remote cluster. See CLI Tools.
- 66. メタデータの除去設定
- 67. 2.2.0 The major enhancements available in Couchbase Server 2.2 include: • XDCR performance optimization through new mode of replication which utilizes highly efficient memcached protocol on the destination cluster for replicating changes. See Behavior and Limitations. 新しい、閲覧専用のアドミニストレータ・ユーザ・アカウントをCouchbase Serverに設定できるように • Disk storage optimization through new metadata purge settings なりました。このユーザは、Couchbase Serverにアクセスし、管理用UI、ツール、そしてREST APIを使 for permanently purge metadata on deleted 用することができますが、すべてリードオンリモードとなります。 items. See Disk Storage. • New read-only admin user to Couchbase Server. This user will have access to Couchbase Server and its Admin UI, tools and REST APIs but only in read-only mode. See Account Management. • New addition to our toolset CBRecovery tool that provides additional durability from remote cluster. See CLI Tools.
- 68. 2.2.0 The major enhancements available in Couchbase Server 2.2 include: • XDCR performance optimization through new mode of replication which utilizes highly efficient memcached protocol on the destination cluster for replicating changes. See Behavior and Limitations. • Disk storage optimization through new metadata purge settings for permanently purge metadata on deleted items. See Disk Storage. • New read-only admin user to Couchbase Server. This user will これまでのコマンドツールに、新たにCBRecoveryツールが加わりました。これは、リモートクラスタに have access to Couchbase Server and its Admin UI, tools and 更なる耐久性を提供します。 REST APIs but only in read-only mode. See Account Management. • New addition to our toolset CBRecovery tool that provides additional durability from remote cluster. See CLI Tools.
- 69. 2.2.0 Additional enhancements in 2.2 include: • Instructions for non-root, non-sudo installation and running of Couchbase Server and its tools. See Installing Couchbase Server. • CRAM-MD5 support for SASL authentication on Couchbase Server. See Providing SASL Authentication. See Couchbase Developer Guide 2.2, ルート権限やsudoを必要としないインストール＆サーバ起動、そしてコマンドラインツールが提供され Providing SASL Authentication ます。 • Ability to reset password for Administrator using the CLI command. See cbreset_password Tool. Fixes in 2.2 • Command-line Tools ◦ In past versions of Couchbase Server, cbbackup would continue past 100% progress. This is due to a a bug in the cbbackup progress indicator and tool behavior. In the past, cbtransfer only accounted for items in RAM in the backup estimate, but would also backup deleted items as well as items read from disk into memory. This resulted in greater than 100% progress being displayed. These issues have been fixed. Issues : MB-8692
- 70. 2.2.0 Additional enhancements in 2.2 include: • Instructions for non-root, non-sudo installation and running of Couchbase Server and its tools. See Installing Couchbase Server. • CRAM-MD5 support for SASL authentication on Couchbase Server. See Providing SASL Authentication. See Couchbase Developer Guide 2.2, Providing SASL Authentication • Ability to reset password for Administrator using the CLI command. See cbreset_password Tool. SASL認証向けに、CRAM-MD5認証方式をサポートするようになりました。 Fixes in 2.2 • Command-line Tools ◦ In past versions of Couchbase Server, cbbackup would continue past 100% progress. This is due to a a bug in the cbbackup progress indicator and tool behavior. In the past, cbtransfer only accounted for items in RAM in the backup estimate, but would also backup deleted items as well as items read from disk into memory. This resulted in greater than 100% progress being displayed. These issues have been fixed. Issues : MB-8692
- 71. 2.2.0 Additional enhancements in 2.2 include: • Instructions for non-root, non-sudo installation and running of Couchbase Server and its tools. See Installing Couchbase Server. • CRAM-MD5 support for SASL authentication on Couchbase Server. See Providing SASL Authentication. See Couchbase Developer Guide 2.2, Providing SASL Authentication • Ability to reset password for Administrator using the CLI command. See cbreset_password Tool. Fixes in 2.2 • Command-line Tools コマンドラインにより、アドミニストレータのパスワードをリセットすることができるようになりまし た。 ◦ In past versions of Couchbase Server, cbbackup would continue past 100% progress. This is due to a a bug in the cbbackup progress indicator and tool behavior. In the past, cbtransfer only accounted for items in RAM in the backup estimate, but would also backup deleted items as well as items read from disk into memory. This resulted in greater than 100% progress being displayed. These issues have been fixed. Issues : MB-8692
- 72. 2.2.0 Additional enhancements in 2.2 include: • Instructions for non-root, non-sudo installation and running of Couchbase Server and its tools. See Installing Couchbase Server. • CRAM-MD5 support for SASL authentication on Couchbase Server. See これまでは、cbbackupは、100%を超えて継続されてきました。これは、cbbackupプログレス表示機能 Providing SASL Authentication. See Couchbase Developer Guide 2.2, とツールの挙動に関するバグでした。また、これまではcbtransferは、バックアップ評価中、RAM内のア Providing SASL Authentication イテムのみをカウントしていました。しかしディスクから読み込まれてメモリ上にあるアイテムだけでな • Ability to reset password for Administrator using the CLI command. See く、そこから削除されたアイテムもバックアップする必要があります。このため100%以上の進 率が表 cbreset_password Tool. 示されていました。今回このバクがフィックスされました。 Fixes in 2.2 • Command-line Tools ◦ In past versions of Couchbase Server, cbbackup would continue past 100% progress. This is due to a a bug in the cbbackup progress indicator and tool behavior. In the past, cbtransfer only accounted for items in RAM in the backup estimate, but would also backup deleted items as well as items read from disk into memory. This resulted in greater than 100% progress being displayed. These issues have been fixed. Issues : MB-8692
- 73. Fixes in 2.2 2.2.0 • Indexing and Querying ◦ In the past you had to delete an XDCR replication and recreate it if you wanted to change any XDCR internal settings. This includes: xdcr_optimistic_replication_threshold, xdcr_worker_batch_size, xdcr_connection_timeout, xdcr_num_worker_process, xdcr_num_http_connections, and xdcr_num_retries_per_request. You can now change these settings and they will immediately apply to the existing XDCR replication. For more information, see Changing Internal XDCR Settings. Issues : MB-8422 • Cross Datacenter Replication (XDCR) これまでは、もしもあなたが、XDCRの内部設定を変更した場合には、いったんXDCR設定を削除し、 ◦ If you used a custom data path then performed a server uninstall 改めて再作成するしかありませんでした。このような設定には以下が含まれます and upgraded, older XDCR replication files were left intact. This resulted in （xdcr_optimistic_replication_threshold, xdcr_worker_batch_size, xdcr_connection_timeout, Couchbase Server xdcr_num_http_connections, xdcr_num_retries_per_request.）。今 xdcr_num_worker_process, crashes and incorrect information in Web Console. This has been fixed. 回から、これらの設定を既に存在するXDCRについて即座に変更することができるようになりました。 Issues : MB-8460
- 74. Fixes in 2.2 2.2.0 • Indexing and Querying ◦ In the past you had to delete an XDCR replication and recreate it if you wanted to change any XDCR internal settings. This includes: xdcr_optimistic_replication_threshold, xdcr_worker_batch_size, xdcr_connection_timeout, xdcr_num_worker_process, xdcr_num_http_connections, and もしもあなたが、カスタムデータパスを使用して、サーバのアンインストールやアップグレードを実行し た場合、古いXDCRレプリケーションファイルは、削除されずに残されていました。これは、Couchbase xdcr_num_retries_per_request. You can now change these settings Serverのクラッシュと、Webコンソールに誤った情報を表示する結果になります。今回この問題をフィッ and they will immediately apply to the existing XDCR replication. For more クスしました。 information, see Changing Internal XDCR Settings. Issues : MB-8422 • Cross Datacenter Replication (XDCR) ◦ If you used a custom data path then performed a server uninstall and upgraded, older XDCR replication files were left intact. This resulted in Couchbase Server crashes and incorrect information in Web Console. This has been fixed. Issues : MB-8460
- 75. 2.2.0 Fixes in 2.2 ◦ Non-UTF-8 encoded keys will not be replicated to destination clusters via XDCR by design. See Behavior and Limitations. Issues : MB-8427 • Performance XDCRでは、設計上、非UTF-8エンコードキーは、レプリケーション先のクラスタにレプリケートされま ◦ Users may experience segmentation faults if a cluster is under heavy stress. For example if your cluster has a very high disk write queue such as 2 million items per node, several XDCR replications, plus thousands of writes per second, the disks will drain slower. With a similar workload and limited hardware, synchronization delays in I/O may occur resulting in a segmentation fault. This may result in data-loss. We therefore recommend you have adequate cluster capacity and monitor operations per second on your cluster. Issues : MB-9098 ◦ Users experienced higher latency rates when they performed observe for せん。 replicated data. We have now fixed the issue. Latency is now at least 5 times faster for this use case for Couchbase Server 2.2. Issues : MB-8453
- 76. 2.2.0 Fixes in 2.2 ◦ Non-UTF-8 encoded keys will not be replicated to destination clusters via XDCR by design. See Behavior and Limitations. Issues : MB-8427 • Performance ◦ Users experienced higher latency rates when they performed observe for replicated data. We have now fixed the issue. Latency is now at least 5 times faster for this use case for Couchbase Server 2.2. Issues : MB-8453 ◦ Users may experience segmentation faults if a cluster is under heavy stress. ユーザは、レプリカデータについて、高いレィテンシレートを経験してきました。今回この問題を解決し For example if your cluster has a very high disk write queue such as 2 million ました。今回のフィックスにより、(レプリケーションが)少なくとも5倍以上高速になりました。 items per node, several XDCR replications, plus thousands of writes per second, the disks will drain slower. With a similar workload and limited hardware, synchronization delays in I/O may occur resulting in a segmentation fault. This may result in data-loss. We therefore recommend you have adequate cluster capacity and monitor operations per second on your cluster. Issues : MB-9098
- 77. 2.2.0 Fixes in 2.2 ◦ Non-UTF-8 encoded keys will not be replicated to destination clusters via XDCR by design. See Behavior and Limitations. ユーザは、クラスタが非常に重い荷重がかかった場合に、セグメンテーションフォールトを経験してきま Issues : MB-8427 した。例えば、クラスタが非常に大量のディスク書込みキュー（例えば1ノードあたり200万アイテム程 • Performance 度）を抱え、いくつかのXDCRレプリケーションが設定されており、1秒間あたり、1000回の書込みが加 えられた場合、ディスクは、徐々に遅くなります。同様のワークロードと制限されたハードウェアで、同 ◦ Users experienced higher latency rates when they performed observe for 期処理の遅延し、I/Oはセグメンテーションフォールトを発生させる結果となるでしょう。これは、デー replicated data. We have now fixed the issue. タロスが起きてしまいます。我々はこのため、適切なクラスタ容量の確保と、クラスタの1秒あたりのオ Latency is now at least 5 times faster for this use case for Couchbase Server 2.2. ペレーション数をモニタリングすることを推奨しています。 Issues : MB-8453 ◦ Users may experience segmentation faults if a cluster is under heavy stress. For example if your cluster has a very high disk write queue such as 2 million items per node, several XDCR replications, plus thousands of writes per second, the disks will drain slower. With a similar workload and limited hardware, synchronization delays in I/O may occur resulting in a segmentation fault. This may result in data-loss. We therefore recommend you have adequate cluster capacity and monitor operations per second on your cluster. Issues : MB-9098
- 79. ９月には 他にもいろいろありました N1QL Couchbase Query Language, known as N1QL or ‘Nickel’, helps you to find and change data in Couchbase Server. We designed the language to be human -readable and -writable; it is an extensible language designed for ad-hoc querying. The query language is a standard semantic you use to build querying ability in other programming languages.