Search:

Search all manuals
Search this manual
Manual
Moxi Server 1.8
Additional Resources
Community Wiki
Community Forums
Couchbase SDKs
Parent Section
Moxi Server 1.8
Child Sections
Chapters

Chapter 3. Standalone Moxi Component

Table of Contents

3.1. Downloading and Installing Standalone Moxi
3.2. Running moxi
3.3. Configuration
3.3.1. Local configuration (moxi.cfg)
3.3.2. Cluster Configuration (moxi-cluster.cfg)
3.4. Advanced Standalone moxi Configuration
3.4. Changing the default listening port
3.4. Specifying SASL authentication
3.4. Increased Logging
3.5. Ascii and Binary Protocols
3.6. Gateway versus bucket-specific moxi's
3.6. Gateway moxi
3.6. Per-Bucket moxi
3.7. Increasing Concurrency
3.7. Increase Worker Threads
3.7. Increase Number of Concurrent Client Requests
3.7. Implications
3.7. Downstream conn queues
3.8. Timeouts
3.9. Configuration File
3.10. Errors
3.10. Command-line and Configuration Errors
3.10. Protocol Errors

Couchbase provides a standalone Moxi component that enables scalable deployments across multiple web application servers. The best practice is to install one standalone Moxi per web application server, and then point web applications to the standalone Moxi instance on its own server. The Moxi component then communicates directly with the Cluster Manager (specified via the HTTP/REST URL supplied upon Moxi startup). This Moxi component communicates with the Cluster Manager and is aware of cluster settings and changes.