Re: Shards cannot be read after move to a different cluster

unsubscribe > On Jul 7, 2022, at 3:29 AM, Luca Morandini wrote: > > Dear All, > > I moved some CouchDB 3.1.0 databases to a new 4-node cluster via > copying the shard files. > > The operation worked for 5 out of 6 databases; the biggest database > (about 200GB, 12 shards, 2 replicas) did not

Shards cannot be read after move to a different cluster

Dear All, I moved some CouchDB 3.1.0 databases to a new 4-node cluster via copying the shard files. The operation worked for 5 out of 6 databases; the biggest database (about 200GB, 12 shards, 2 replicas) did not come online on the new cluster. I suspect high disk latency, but... could someone s