Details
-
Bug
-
Resolution: Fixed
-
Test Blocker
-
6.5.0
-
Centos 7.6
-
Triaged
-
Yes
Description
Step to reproduce:
- Install Couchbase server 6.5.0-4106 on a centos 7.6 server.
- Set services kv,index,n1ql,fts on this single node A
- Create default bucket.
- Load 20 items to default bucket.
- Create backup repo
- Run backup to backup 20 items
- Add 10 items, update and delete items in bucket (only 12 items left).
- Run backup again
- Run one more backup again
- Merge these all 3 backups.
- Run list data in backup repo, failed to list backup (error: backup is either empty or it got interrupted)
- Create default bucket in other single node B.
- Restore data back to node B.
- Default bucket in node B has 30 items. It should have only 12 items as in default bucket in node A
2019-08-27 23:11:00 | INFO | MainProcess | test_thread | [remote_util.execute_command_raw] running command.raw on 172.23.121.227: /opt/couchbase/bin//cbbackupmgr list --archive /tmp/entbackup
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.execute_command_raw] command executed successfully
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] Backup `/tmp/entbackup/backup/2019-08-27T23_10_49.94571982-07_00/default-cb5071ddb48cf2430ecbdac12969bb67/data` is either empty or it got interrupted
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] Size Items Name
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 197.25MB - /
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 197.25MB - + backup
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 67.75MB - + 2019-08-27T23_08_20.165074732-07_00
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 67.75MB - + default
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 0B 0 analytics.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 410B 0 bucket-config.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 67.75MB 30 + data
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 67.75MB 30 1024 Shards
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 2B 0 full-text.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 227B 0 gsi.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 2B 0 views.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 65.50MB - + 2019-08-27T23_09_36.161839335-07_00
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 65.50MB - + default
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 0B 0 analytics.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 410B 0 bucket-config.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 65.50MB 12 + data
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 65.50MB 12 1024 Shards
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 2B 0 full-text.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 227B 0 gsi.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 2B 0 views.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 64.00MB - + 2019-08-27T23_10_49.94571982-07_00
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 64.00MB - + default
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 0B 0 analytics.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 410B 0 bucket-config.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 64.00MB 0 + data
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 64.00MB 0 1024 Shards
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 2B 0 full-text.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 227B 0 gsi.json
|
2019-08-27 23:11:01 | INFO | MainProcess | test_thread | [remote_util.log_command_output] 2B 0 views.json
|
|
It could be easy reproduce with this test with 1 server
ent_backup_restore.enterprise_backup_merge_tests.EnterpriseBackupMergeTest.test_multiple_backups_merges,actions="backup_with_ops:2,backup:1,merge:1&3",get-coredumps=False,force_kill_memached=True,verify_unacked_bytes=True,items=2
Attachments
Issue Links
- relates to
-
MB-35728 cbbackupmgr stats are incorrect after a merge
- Closed