DOCSLIB.ORG

Couchbase Server Manual 2.1.0 Couchbase Server Manual 2.1.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Couchbase Server Manual 2.1.0 Couchbase Server Manual 2.1.0 Couchbase Server Manual 2.1.0 Couchbase Server Manual 2.1.0 Abstract This manual documents the Couchbase Server 2.1.0 series, including installation, monitoring, and administration interface and associ- ated tools. For the corresponding Moxi product, please use the Moxi 1.8 series. See Moxi 1.8 Manual. External Community Resources. Download Couchbase Server 2.1 Couchbase Developer Guide 2.1 Client Libraries Couchbase Server Forum Last document update: 05 Sep 2013 23:46; Document built: 05 Sep 2013 23:46. Documentation Availability and Formats. This documentation is available online: HTML Online . For other documentation from Couchbase, see Couchbase Documentation Library Contact: [email protected] or couchbase.com Copyright © 2010-2013 Couchbase, Inc. Contact [email protected]. For documentation license information, see Section F.1, “Documentation License”. For all license information, see Appendix F, Licenses. Table of Contents Preface ................................................................................................................................................... xiii 1. Best Practice Guides ..................................................................................................................... xiii 1. Introduction to Couchbase Server .............................................................................................................. 1 1.1. Couchbase Server and NoSQL ........................................................................................................ 1 1.2. Architecture and Concepts ............................................................................................................. 2 1.2.1. Nodes and Clusters ............................................................................................................ 2 1.2.2. Cluster Manager ................................................................................................................ 2 1.2.3. Data Storage ..................................................................................................................... 3 1.2.4. RAM Quotas ..................................................................................................................... 5 1.2.5. vBuckets .......................................................................................................................... 6 1.2.6. Caching Layer ................................................................................................................... 7 1.2.7. Disk Storage ..................................................................................................................... 8 1.2.8. Ejection, Eviction and Working Set Management ..................................................................... 9 1.2.9. Expiration ....................................................................................................................... 11 1.2.10. Server Warmup .............................................................................................................. 11 1.2.11. Rebalancing ................................................................................................................... 11 1.2.12. Replicas and Replication .................................................................................................. 11 1.2.13. Failover ........................................................................................................................ 12 1.2.14. TAP ............................................................................................................................. 12 1.2.15. Client Interface .............................................................................................................. 12 1.2.16. Administration Tools ....................................................................................................... 13 1.2.17. Statistics and Monitoring ................................................................................................. 14 1.3. Migration to Couchbase ............................................................................................................... 14 1.3.1. Migrating for Membase Users ............................................................................................ 15 1.3.2. Migrating for CouchDB Users ............................................................................................ 16 2. Installing and Upgrading ........................................................................................................................ 18 2.1. Preparation ................................................................................................................................ 18 2.1.1. Supported Platforms ......................................................................................................... 18 2.1.2. Resource Requirements ..................................................................................................... 19 2.1.3. Supported Web Browsers .................................................................................................. 19 2.1.4. Network Ports ................................................................................................................. 20 2.2. Installing Couchbase Server .......................................................................................................... 21 2.2.1. Red Hat Linux Installation ................................................................................................. 21 2.2.2. Ubuntu Linux Installation .................................................................................................. 22 2.2.3. Microsoft Windows Installation .......................................................................................... 22 2.2.4. Mac OS X Installation ...................................................................................................... 24 2.3. Initial Server Setup ..................................................................................................................... 25 2.4. Using Hostnames with Couchbase Server ........................................................................................ 29 2.4.1. Hostnames for Couchbase Server 2.0.1 and Earlier ................................................................. 31 2.5. Upgrading to Couchbase Server 2.1 ............................................................................................... 33 2.5.1. Online Upgrade with Swap Rebalance ................................................................................. 34 2.5.2. Standard Online Upgrades ................................................................................................. 36 2.5.3. Offline Upgrade Process .................................................................................................... 38 2.6. Upgrading Individual Nodes ......................................................................................................... 39 2.7. Upgrades Notes 1.8.1 to 2.1 ......................................................................................................... 40 2.7.1. Upgrade Notes 1.8 and Earlier to 2.1+ ................................................................................. 41 2.7.2. Upgrading from Community Edition to Enterprise Edition ....................................................... 41 2.8. Testing Couchbase Server ............................................................................................................ 42 2.8.1. Testing Couchbase Server using cbworkloadgen ................................................................... 42 2.8.2. Testing Couchbase Server using Telnet ................................................................................ 42 2.9. Next Steps ................................................................................................................................. 43 iii Couchbase Server Manual 2.1.0 3. Administration Basics ............................................................................................................................ 44 3.1. Couchbase Data Files .................................................................................................................. 44 3.2. Server Startup and Shutdown ........................................................................................................ 45 3.2.1. Startup and Shutdown on Linux .......................................................................................... 45 3.2.2. Startup and Shutdown on Windows ..................................................................................... 45 3.2.3. Startup and Shutdown on Mac OS X ................................................................................... 46 4. Best Practices ....................................................................................................................................... 49 4.1. Cluster Design Considerations ...................................................................................................... 49 4.2. Sizing Guidelines ........................................................................................................................ 49 4.2.1. RAM Sizing .................................................................................................................... 50 4.2.2. Disk Throughput and Sizing ............................................................................................... 52 4.2.3. Network Bandwidth .........................................................................................................
Load more

Recommended publications
  • MCP Q4`18 Release Notes Version Q4-18 Mirantis Cloud Platform Release Notes Version Q4`18
    MCP Q4`18 Release Notes version q4-18 Mirantis Cloud Platform Release Notes version Q4`18 Copyright notice 2021 Mirantis, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. No part of this publication may be reproduced in any written, electronic, recording, or photocopying form without written permission of Mirantis, Inc. Mirantis, Inc. reserves the right to modify the content of this document at any time without prior notice. Functionality described in the document may not be available at the moment. The document contains the latest information at the time of publication. Mirantis, Inc. and the Mirantis Logo are trademarks of Mirantis, Inc. and/or its affiliates in the United States an other countries. Third party trademarks, service marks, and names mentioned in this document are the properties of their respective owners. ©2021, Mirantis Inc. Page 2 Mirantis Cloud Platform Release Notes version Q4`18 What’s new This section provides the details about the features and enhancements introduced with the latest MCP release version. Note The MCP integration of the community software projects, such as OpenStack, Kubernetes, OpenContrail, and Ceph, includes the integration of the features which the MCP consumers can benefit from. Refer to the MCP Q4`18 Deployment Guide for the software features that can be deployed and managed by MCP DriveTrain. MCP DriveTrain • Encryption of sensitive data in the Reclass model • Galera verification and restoration pipeline • Jenkins version upgrade • Partitioning table for the VCP images Encryption of sensitive data in the Reclass model SECURITY Implemented the GPG encryption to protect sensitive data in the Git repositories of the Reclass model as well as the key management mechanism for secrets encryption and decryption.
    [Show full text]
  • LIST of NOSQL DATABASES [Currently 150]
    Your Ultimate Guide to the Non - Relational Universe! [the best selected nosql link Archive in the web] ...never miss a conceptual article again... News Feed covering all changes here! NoSQL DEFINITION: Next Generation Databases mostly addressing some of the points: being non-relational, distributed, open-source and horizontally scalable. The original intention has been modern web-scale databases. The movement began early 2009 and is growing rapidly. Often more characteristics apply such as: schema-free, easy replication support, simple API, eventually consistent / BASE (not ACID), a huge amount of data and more. So the misleading term "nosql" (the community now translates it mostly with "not only sql") should be seen as an alias to something like the definition above. [based on 7 sources, 14 constructive feedback emails (thanks!) and 1 disliking comment . Agree / Disagree? Tell me so! By the way: this is a strong definition and it is out there here since 2009!] LIST OF NOSQL DATABASES [currently 150] Core NoSQL Systems: [Mostly originated out of a Web 2.0 need] Wide Column Store / Column Families Hadoop / HBase API: Java / any writer, Protocol: any write call, Query Method: MapReduce Java / any exec, Replication: HDFS Replication, Written in: Java, Concurrency: ?, Misc: Links: 3 Books [1, 2, 3] Cassandra massively scalable, partitioned row store, masterless architecture, linear scale performance, no single points of failure, read/write support across multiple data centers & cloud availability zones. API / Query Method: CQL and Thrift, replication: peer-to-peer, written in: Java, Concurrency: tunable consistency, Misc: built-in data compression, MapReduce support, primary/secondary indexes, security features.
    [Show full text]
  • High Performance with Distributed Caching
    High Performance with Distributed Caching Key Requirements For Choosing The Right Solution High Performance with Distributed Caching: Key Requirements for Choosing the Right Solution Table of Contents Executive summary 3 Companies are choosing Couchbase for their caching layer, and much more 3 Memory-first 4 Persistence 4 Elastic scalability 4 Replication 5 More than caching 5 About this guide 5 Memcached and Oracle Coherence – two popular caching solutions 6 Oracle Coherence 6 Memcached 6 Why cache? Better performance, lower costs 6 Common caching use cases 7 Key requirements for an effective distributed caching solution 8 Problems with Oracle Coherence: cost, complexity, capabilities 8 Memcached: A simple, powerful open source cache 10 Lack of enterprise support, built-in management, and advanced features 10 Couchbase Server as a high-performance distributed cache 10 General-purpose NoSQL database with Memcached roots 10 Meets key requirements for distributed caching 11 Develop with agility 11 Perform at any scale 11 Manage with ease 12 Benchmarks: Couchbase performance under caching workloads 12 Simple migration from Oracle Coherence or Memcached to Couchbase 13 Drop-in replacement for Memcached: No code changes required 14 Migrating from Oracle Coherence to Couchbase Server 14 Beyond caching: Simplify IT infrastructure, reduce costs with Couchbase 14 About Couchbase 14 Caching has become Executive Summary a de facto technology to boost application For many web, mobile, and Internet of Things (IoT) applications that run in clustered performance as well or cloud environments, distributed caching is a key requirement, for reasons of both as reduce costs. performance and cost. By caching frequently accessed data in memory – rather than making round trips to the backend database – applications can deliver highly responsive experiences that today’s users expect.
    [Show full text]
  • Database Software Market: Billy Fitzsimmons +1 312 364 5112
    Equity Research Technology, Media, & Communications | Enterprise and Cloud Infrastructure March 22, 2019 Industry Report Jason Ader +1 617 235 7519 [email protected] Database Software Market: Billy Fitzsimmons +1 312 364 5112 The Long-Awaited Shake-up [email protected] Naji +1 212 245 6508 [email protected] Please refer to important disclosures on pages 70 and 71. Analyst certification is on page 70. William Blair or an affiliate does and seeks to do business with companies covered in its research reports. As a result, investors should be aware that the firm may have a conflict of interest that could affect the objectivity of this report. This report is not intended to provide personal investment advice. The opinions and recommendations here- in do not take into account individual client circumstances, objectives, or needs and are not intended as recommen- dations of particular securities, financial instruments, or strategies to particular clients. The recipient of this report must make its own independent decisions regarding any securities or financial instruments mentioned herein. William Blair Contents Key Findings ......................................................................................................................3 Introduction .......................................................................................................................5 Database Market History ...................................................................................................7 Market Definitions
    [Show full text]
  • Couchbase Vs Mongodb Architectural Differences and Their Impact
    MongoDB vs. Couchbase Server: Architectural Differences and Their Impact This 45-page paper compares two popular NoSQL offerings, diving into their architecture, clustering, replication, and caching. By Vladimir Starostenkov, R&D Engineer at Altoros Q3 2015 Table of Contents 1. OVERVIEW ......................................................................................................................... 3 2. INTRODUCTION ................................................................................................................. 3 3. ARCHITECTURE................................................................................................................. 4 4. CLUSTERING ..................................................................................................................... 4 4.1 MongoDB ............................................................................................................................................. 4 4.2 Couchbase Server .............................................................................................................................. 5 4.3 Partitioning .......................................................................................................................................... 6 4.4 MongoDB ............................................................................................................................................. 7 4.5 Couchbase Server .............................................................................................................................
    [Show full text]
  • THE NOTION of DESIGN EMERGENCE EVOLVING YOUR SOFTWARE Who Are We
    THE NOTION OF DESIGN EMERGENCE EVOLVING YOUR SOFTWARE Who Are we 陈永胜 [email protected] @yeongsheng yeongsheng-tan !2 EVOLVING YOUR SOFTWARE - THE NOTION OF DESIGN EMERGENCE “THE BEST ARCHITECTURES, REQUIREMENTS, AND DESIGNS EMERGE FROM SELF-ORGANIZING TEAMS.” – PRINCIPLES BEHIND THE AGILE MANIFESTO AGENDA ‣ EMERGENT DESIGN ‣ CHOOSE YOUR POISON ‣ SWITCHING OUT AN ARCHITECTURAL LAYER ‣ WHEN RUBBER HITS THE ROAD ‣ SHOW ME THE CODE ‣ Q&A LISTEN, LEARN, UNDERSTAND, ADAPT EMERGENT DESIGN EVOLVING YOUR SOFTWARE - THE NOTION OF DESIGN EMERGENCE KNOWLEDGE CREATION & PRESERVATION KNOWLEDGE CREATION KNOWLEDGE PRESERVATION EVOLVING YOUR SOFTWARE - THE NOTION OF DESIGN EMERGENCE WHEN DO YOU HAVE BEST KNOWLEDGE? KNOWLEDGE VS TIME 100 75 50 Knowledge 25 0 AUG SEP OCT NOV DEC Time EVOLVING YOUR SOFTWARE - THE NOTION OF DESIGN EMERGENCE HYPOTHETICAL KNOWLEDGE VS TIME 100 75 50 Knowledge 25 0 AUG SEP OCT NOV DEC Time EVOLVING YOUR SOFTWARE - THE NOTION OF DESIGN EMERGENCE REALITY KNOWLEDGE VS TIME 100 75 50 Knowledge 25 0 AUG SEP OCT NOV DEC Time EVOLVING YOUR SOFTWARE - THE NOTION OF DESIGN EMERGENCE WHAT WE SHOULD STRIVE FOR KNOWLEDGE VS TIME 100 75 50 Knowledge 25 0 AUG SEP OCT NOV DEC Time EVOLVING YOUR SOFTWARE - THE NOTION OF DESIGN EMERGENCE TRADITIONAL VS EMERGENT Design Implement the initial design (try to make all decisions) TRADITIONAL EMERGENT Design Reflect and (decide an Design/Code Decide Design/Code initial Direction direction) Reflect and Design/Code Decide Direction EVOLVING YOUR SOFTWARE - THE NOTION OF DESIGN EMERGENCE MAKE IT WORK
    [Show full text]
  • Designing a Modern XMPP Service with Ejabberd
    ejabberd architecture and challenges in designing a modern messaging service 17th November 2015 Mickaël Rémond <[email protected]> Introduction ejabberd is scalable and versatile enough to adapt to most of the realtime messaging jobs you will want to handle. For many tasks, like corporate messaging, you can consider ejabberd as a standard package. However, to reach high level of scalability and flexibility, you need to consider ejabberd as an XMPP framework. As such, to build your modern messaging system, you need to: Be familiar with XMPP - Prerequisite. Learn ejabberd architecture Learn ejabberd API Work on solution design. Take control of your messaging platform and design it ! ejabberd: Routing messages in a statefull world ejabberd is a message router. Its role is to support real time messaging feature by moving messages from clients to other clients. In that sense it is stateless. However, to integrate in a statefull world, ejabberd has to support statefull features: Stateless: ejabberd is an XMPP server: Its goal is to route XMPP packets between JID. Statefull: In most case ejabberd depends on data (user base, contact list, …) or produce data (message archive, ...) Goal: deploy an ejabberd that is as stateless as possible, by leveraging backends. What are ejabberd backends ? Backends are pluggable modules you can configure to define where you would like to store part or all of your data. Backends provide the data to the feature modules of ejabberd. They can be read-write or read-only if you do not need some of the ejabberd associated features: For example, if you handle user management elsewhere in your infrastructure, you can use a user back-end that can only authenticate users but not create them.
    [Show full text]
  • Document Store Database Example
    Document Store Database Example Roderich is Barmecide: she predefine originally and juicing her currants. Prototypal Eli still utilises: purgatorial and associate Ron dimes quite eerily but drift her equalisers abidingly. Very and tantalizing Rikki luminesces, but Davis leftwardly rightens her docks. Returns an idea of database document model needs with each also accepts parameters such as strings Break when out nor the JSON and have it light an explicit issue in a hybrid store. Running a document database on Sql Server. Documents are stored in Collections and glide their dedicated CRUD operation set. How they use SQL Server as a Document Store Octopus Deploy. Examples of RDBMS and NoSQL databases Rackspace. MySQL JSON Document Store dasininet Diary create a MySQL. Tinydb PyPI. A database document store represents a collection of documents imported into. As we knew also see play are four tables in the worldx database but db. 3Pillar blog post by Girish Kumar and Rahul Checker exploring the different types of NoSQL databases that you cancel consider for each enterprise needs. How will data here a document database also possess as an own database stored? Document databases make it easier for developers to display and hence data in most database. Why You mother Never Use MongoDB Sarah Mei. For utility if you now looking at video surveillance data sensor. NoSQL Tutorial Types of NoSQL Databases What is & Example. To connect an obedience of the DocumentStore you need to abduct a best of URL addresses that compassion to RavenDB server nodes new DocumentStoreurls database. Xml document store lists of document stores do the database store and console gamer, specially if available.
    [Show full text]
  • CV 4567 Technical Lead / System Architect / Senior Erlang Developer / Senior UI/UX Developder/ Designer
    CV_4567 Technical lead / System architect / Senior Erlang Developer / Senior UI/UX developder/ designer Free for offers. For now I am fully concentrated on Erlang and on all that connected to it. My last position is Technical Lead within experience of managing and building client-server application for both side: server or client. My experience is: Software Developer Skill: over 14 years Erlang Developing: over 6 years High-load Developing: over 10 years Big-Data Developing: 4 years Qt/QML Interfaces Developing: 5 years Web/UI/UX Designer Skill: over 16 years Designer Skill: over 23 years Management Skill: over 14 years And other, other, other ... I know and have comprehension of different: - in design: minimalism style vs. have no any ability to create something - in development: reinvent the wheel vs. have no any wishes for to do something - in management: the answer to the problem vs. fitting answer Career Owner / Technical lead, Erlang Web Developer, Senior UI/UX/Designer September 2012 - Aktuell I am supporting this project for my own experiments and gathering results of it. Full stack Erlang Web developer 1. Library for Yaws 2. HTML Render Engine for Yaws 3. Mnesia clustering 4. Trademark naming 5. Design: branding/UI/UX/Web Technical lead / System architect / Senior Erlang Developer / Senior UI/UX developder/designer Mai 2016 - April 2018 I've done for this company (all is HIPAA-compliant): 1) Architectural projecting: -- protocol for instant messenger via HTTPS -- message DB structure -- cluster architecture -- search engine emulation
    [Show full text]
  • Distributed Event Handler
    Distributed Event Handler Creation of a distributed event handler with priority handling and synchronized timing ROBIN OLAUSSON JIMMY WESTERLUND Degree project in Information and Software systems Stockholm, Sweden 2013 TRITA-ICT-EX-2013:163 Distributed Event Handler Creation of a distributed event handler with priority handling and synchronized timing ROBIN OLAUSSON, JIMMY WESTERLUND Bachelor Thesis at ICT Examiner: Johan Montelius (School of ICT) Abstract During the start up of a project, we found out that an event handler was needed. This event handler needed to be redundant and able to ensure that events with dependencies to each other, where executed in a specified correct order. Policies where written to ensure that the end result, if able to fulfill these, was the product that was needed. The result is an event handler written in Erlang, which ensures that all events given to it will be executed in the order specified. Even though not fulfilling all policies there are plans for future work with solutions on how this will be fixed. In conclusion, even though the event handler is not a complete product, this report presents a solution to the general event handling problem. Referat Ditribuerad Händelsehanterare Under uppstarten av ett projekt fick vi reda p˚aatt det beh¨ovdes en h¨andelsehanterare. H¨andelsehanteraren skulle vara redundant och kunna s¨akerst¨alla att h¨andelser beroende av varandra, k¨ordes i den ordning som specifiserats. Policies skrevs ner f¨or att f¨ors¨akra att om h¨andelsehanteraren kunde uppfylla dessa, var detta produkten som efters¨oktes. Re- sultatet blev en h¨andelsehanterare skriven i Erlang, vilken f¨ors¨akrar att samtliga event givna, blev utf¨orda i den spec- ifierade ordningen.
    [Show full text]
  • Mnesia Database Managment System (MNESIA)
    Mnesia Database Managment System (MNESIA) version 3.9 Typeset in LATEX from SGML source using the DOCBUILDER 3.0 Document System. Contents 1 MNESIA User's Guide 1 1.1 Introduction ......................................... 2 AboutMnesia......................................... 2 TheMnesiaDataBaseManagementSystem(DBMS)................... 3 1.2 GettingStartedwithMnesia ................................ 6 StartingMnesiaforthe®rsttime............................... 6 Anintroductoryexample................................... 7 1.3 BuildingAMnesiaDatabase................................. 16 De®ningaSchema...................................... 16 Thedatamodel........................................ 17 StartingMnesia........................................ 18 CreatingNewTables..................................... 20 1.4 Transactions and other access contexts . 23 TransactionProperties.................................... 23 Locking............................................ 25 DirtyOperations....................................... 28 Record names versus table names . 29 Activity concept and various access contexts . 31 Nestedtransactions...................................... 33 Patternmatching....................................... 33 1.5 MiscellaneousMnesiaFeatures............................... 35 Indexing............................................ 35 DistributionandFaultTolerance.............................. 36 TableFragmentation..................................... 37 Localcontenttables...................................... 42 Disc-lessnodes.......................................
    [Show full text]
  • APPLICATION of BLOCKCHAIN NETWORK for the USE of INFORMATION SHARING by Linir Zamir
    APPLICATION OF BLOCKCHAIN NETWORK FOR THE USE OF INFORMATION SHARING by Linir Zamir A Thesis Submitted to the Faculty of The College of Engineering and Computer Science in Partial Fulfillment of the Requirements for the Degree of Master of Science Florida Atlantic University Boca Raton, FL August 2019 Copyright 2019 by Linir Zamir ii ACKNOWLEDGEMENTS I would like to thank my committee members: Dr. Feng-Hao Liu, my commit- tee chair; Dr. Mehrdad Nojoumian and Dr. Elias Bou-Harb for their encouragement, insightful comments and hard questions. I would also like to thank my mother, who supported me with love and understanding. Without you, I could never have made it this far in my academical studies and generally in life. iv ABSTRACT Author: Linir Zamir Title: Application of Blockchain networkfor the use of Information Sharing Institution: Florida Atlantic University Thesis Advisor: Dr. Feng-Hao Liu Degree: Master of Science Year: 2019 The Blockchain concept was originally developed to provide security in the Bitcoin cryptocurrency network, where trust is achieved through the provision of an agreed-upon and immutable record of transactions between parties. The use of a Blockchain as a secure, publicly distributed ledger is applicable to fields beyond finance, and is an emerging area of research across many other fields in the industry. This thesis considers the feasibility of using a Blockchain to facilitate secured infor- mation sharing between parties, where a lack of trust and absence of central control are common characteristics. Implementation of a Blockchain Information Sharing system will be designed on an existing Blockchain network with as a communicative party members sharing secured information.
    [Show full text]