Vishnu
April 24, 2020, 1:29pm
1
cbbackupmgr merge takes a lot of time. It has been running for more than 5 hours and it shows the same status in .merge_status file
{
"merge_dir": "/home/azuser/couchbase_backup_data/incr_bucket/merge_archive/2020-04-21T18:20:04/incr_bucket/.merge",
"name": "2020-04-23T17_32_05.549326531+01_00",
"merging": [
"2020-04-23T08_40_04.202944723+01_00",
"2020-04-23T09_40_03.980168977+01_00",
"2020-04-23T10_00_04.431288026+01_00",
"2020-04-23T10_20_04.437950042+01_00",
"2020-04-23T17_32_05.549326531+01_00"
],
"initial_merge_complete": false,
"dir_removal_complete": false
}
First backup has 16 million records in the bucket. Is such a kind of time expected?
Couchbase 6.0.x
VM spec where merge is run - 4 core cpu, 8 gb ram
Can anyone please help to debug?
Hello Vishnu,
Merge in Couchbase Server 6.0.X can be slow, the good new is that in Couchbase Server 6.5.0 it should be a lot faster. I would recommend upgrading and using the 6.5.0 to do the merge.
Kind regards,
Patrick
Vishnu
April 27, 2020, 11:42am
3
Thank you Patrick. I’ll try that and come back.
There was a small bug in 6.5.0 where merge would fail with large data sets, which is fixed in 6.5.1. Please use that version.
Vishnu
April 28, 2020, 1:36pm
5
I’ve tried 6.5.0 Patrick and i should say it is amazing. Backup, merge and restore takes only 1/5 of what it used to take. Thank you very much
Regards
Vishnu
1 Like
Vishnu
April 29, 2020, 9:02am
6
Is this the error you were referring to Patrick?
Error merging data: no such table: partition830
Regards
Vishnu
Vishnu
April 29, 2020, 9:21am
7
Upgraded to 6.5.1 and the above merge error is gone
1 Like
Yep that was the merge issue I was talking about glad to see it’s working for you.