Details
Major Description
ISSUE
Few Eventing REST calls are failing with ERR_CLUSTER_VERSION against master builds.
Example -
2022-04-20T21:10:23.888-07:00 [Info] ServiceMgr::compareEventingVersionOnNodes eventing version for all nodes: [evt-0.0.0-2751-ee] need version: 6.5 |
2022-04-20T21:10:23.888-07:00 [Warn] ServiceMgr::savePrimaryStore Version compat check failed: All eventing nodes in the cluster must be on version 6.5 or higher for allowing mutations against source bucket |
Attachments
Activity
master builds are always 0.0.0. This certainly isn't going to change. I've suggested in the past that it's dangerous for eventing to do specific version-number comparisons for exactly that reason.
master builds aren't really intended for any kind of testing or use; they exist pretty much solely to be an early-warning system of code integration problems that lead to build breakages.
If you want to be testing post-Neo builds for some reason, you should be using Morpheus (7.2.0) builds.
Handler is doing source bucket mutations. This feature is introduced in couchbase server 6.5
Eventing is checking whether other eventing nodes are on or above 6.5 or not.
Looking at the couchbase version its 0.0.0-2751
2022-04-20T21:00:59.053-07:00, menelaus_web_sup:1:info:web start ok(ns_1@cb.local) - Couchbase Server has started on web port 8091 on node 'ns_1@cb.local'. Version: "0.0.0-2751-enterprise".Chris Hillery, could you please take a look?