Couchbase server is in constant rebalance with key length error even after flushing all data


We have a couchbase server cluster. It has been constantly doing rebalance with error “key length exceeds 250”. Initially the suspicion was that some of the data is causing the problem. So we have flushed data in bucket. It is still trying rebalance with no success.

Rebalance exited with reason {mover_crashed,
<<"{\"error\":{\"context\":\"Key length exceeds 250\"}}">>},

Additional details:

  • Using couchbase kubernetes operator
  • image: couchbase/server:6.6.0

Apparently it’s not a document key length issue, it looked like an issue with pod hostname. When we reduced the size of the cluster name/label etc and redeployed it. The error seems to go away (we may need to monitor for few days).

One thing I am not confident about is, since we did redeploy and hostname change together. I am not sure which one action exactly fixed the issue or the combination.

It would be great if someone can clarify that.

That is correct, this is a limitation on the cluster name itself. There should be a fix for this in 6.6.4

1 Like