Couchbase vbuckets for Magma Storage Engine

Couchbase Server Kubernetes
1

Hi Team,

While reviewing new features of CB 8.0, we noticed that the Magma storage engine reduced vbuckets from 1024 to 128. Could you explain why Couchbase made this change?
Previous CB versions created 1024 vbuckets for the Magma storage backend. We plan to upgrade our clusters to CB 8.0 next quarter and want to understand the benefits of this change.

Also, will migrating existing buckets from Couchstore to Magma affect performance due to this num of vbucket difference?

Thanks,

Debasis

2

The number of vbuckets is configuable in 8.0.
Going from 1024 to 128 reduces the amount of per-vbucket resources, thus improving performance. (On MacOS, the numbet of vbuckets has always been 64)

3

Thanks @mreiche . As per above question so during migration it will not create any issues.

Thanks,

Debasis

4

Before upgrading, consider the following version compatibility concerns.

New Default Storage Backend in Couchbase Server Version 8.0

After you have fully upgraded a cluster to Couchbase Server 8.0.x and later, the default storage backend for buckets is Magma with 128 vBuckets. Previous versions of Couchbase Server used Couchstore with 1024 vBuckets as the default storage backend.

This new default results in two behavior changes from previous versions:

It’s in the documentation.