Repository navigation
Setup cushbase as a storage engine #71
Replies: 4 comments 2 replies
|
Hi there! Oh dear, I'm SO SORRY you found the old Couchbase engine docs 😞 😭 The Couchbase storage engine is extremely old, out of date, and no longer supported. I am extremely sorry it is still listed on the pixl-server-storage page. It was on my TODO list to remove it entirely, because it is incredibly difficult to get working and support. Can I possibly convince you to move to something else? The recommended solution for external storage is an S3-compatible data store, like MinIO. Setup guide: https://github.com/jhuckaby/pixl-server-storage#s3-compatible-services I'm so terribly sorry that I cannot offer support for Couchbase. It would eat my entire life, and I'd be on support calls 24x7. |
|
I'll update the xyOps docs with an official setup guide for MinIO. |
|
Here is the MinIO setup guide: https://github.com/pixlcore/xyops/blob/main/docs/hosting.md#external-storage |
|
I really liked the idea of Cushbase because of the cache and persistence. I'm going to look into MinIO and the different options because I'm not convinced by the default combination of filesystem and SQLite for a high load volume (perhaps 2,000 or 2,500 jobs per minute). In the documentation, you say that if MinIO is used, it can be used alone without the need for the hybrid option. My question is, in that case, could MinIO and Redis be used at the same time? Or is it a problem to have both in hybrid mode? I mean, they would overlap and instead of optimizing performance, it would make it worse. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am installing xyops and, instead of using SQLite, I am working with Cushbase. It is the alternative that seems most suitable for my requirements and that I have found the documentation offered by the storage. After several hours of testing, I am beginning to see the light at the end of the tunnel. But now I have reached a point where I am not making any progress.
I installed the latest version of Couchbase Community Edition 7.6.2 and configured my first bucket to test it out named "xyops_test".
When starting the container, I noticed that the Couchbase client is not installed in the Docker image for version 0.9.35.
The next step was to install the Couchbase v2 client. I got the information from here. https://pixlcore.com/view/pixl-server-storage#couchbase. I created my own Docker container with the latest version of xyops and installed the client with the npm package.
The parameters I have created in config.json are as follows:
Once the container has finally started, I keep going over the information in this log and can't seem to get out of this loop.
| xyOps > xyOps v0.9.35 Starting Up | {"pid":1,"ppid":0,"node":"v22.22.0","arch":"x64","platform":"linux","argv":["/usr/local/bin/node","/opt/xyops/lib/main.js","--foreground"],"execArgv":["--max-old-space-size=4096"]} | xyOps > Server Info: | {"hostname":"infinity-jobs-01","ip":"172.18.0.2","daemon":false} | xyOps > Starting component: Storage | xyOps > Starting component: Unbase | Unbase > Setting up Unbase v1.0.12 | ❌ Error > Couchbase | couchbase | Failed to fetch key: unbase/indexes/data: Client-Side timeout exceeded for operation. Inspect network conditions or increase the timeout | Unbase > Initializing index: jobs | Unbase > Initializing index: alerts | Unbase > Initializing index: snapshots | Unbase > Initializing index: servers | Unbase > Initializing index: activity | Unbase > Initializing index: tickets | xyOps > Starting component: WebServer | xyOps > Starting component: API | API > API service listening for base URI: /api | xyOps > Starting component: User | User > User Manager starting up | API > Adding API namespace: user | xyOps > Starting component: Debug | xyOps > Starting component: xyOps | xyOps > xyOps engine starting up | ["/usr/local/bin/node","/opt/xyops/lib/main.js","--foreground"] | xyOps > Local server time is: Thu Jan 22 2026 20:05:26 GMT+0100 (Central European Standard Time) | ❌ Error > Couchbase | couchbase | Failed to store object: test/750c2bf8ca677cd6ec8889e89259e383: Client-Side timeout exceeded for operation. Inspect network conditions or increase the timeout | ❌ Error > xyOps | startup | Component startup error: Error: Initial storage test failed: Failed to store object: test/750c2bf8ca677cd6ec8889e89259e383: Client-Side timeout exceeded for operation. Inspect network conditions or increase the timeout | xyOps > Component startup error: Error: Initial storage test failed: Failed to store object: test/750c2bf8ca677cd6ec8889e89259e383: Client-Side timeout exceeded for operation. Inspect network conditions or increase the timeout | xyOps > Shutting down | ❌ Error > xyOps | 1 | Startup process was interrupted, exitingAny ideas on what to try? Thanks in advance.
All reactions