Search:

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

Chapter 8. Moxi Design Internals

Table of Contents

8.1. Guiding Ideas
8.2. Key Dependencies
8.3. Key Modules / Files
8.4. Command-Line Configuration
8.4.1. Specifying a cluster
8.4.2. Optional configuration parameters
8.4.3. Config Files
8.4.4. Multi-cluster configuration
8.4.5. Zstored inherited configuration
8.5. Threading
8.5.1. Worker Threads
8.6. Startup Sequences
8.6. Static Configuration Startup Sequence
8.6. Dynamic Configuration Startup Sequence
8.7. Inter-Thread Communcation & Work Queues
8.7. Work Tasks
8.7. Work Queues & Libevent
8.7. Asynchronous vs Synchronous Work Tasks
8.7. Scatter/Gather Work Tasks
8.8. Re-configuration
8.8. Configuration Lock Avoidance & Versioning
8.8. Integration with Libconflate
8.8. One JSON message has all buckets
8.8. Main thread's list of proxies
8.8. proxy vs proxy_td
8.8. Worker threads handle a proxy_td change.

moxi was started around Q1 2009 based off the memcached code base. It's current source repository is a http://github.com/couchbase/moxi.

Moxi inherited a lot of machinery from memcached, including:

From the point of view of moxi's codebase:

Moxi code also uses the word "pool" in a way that predates our modern usage of "cluster", so they are somewhat synonyms.