Multisite sync policy configuration - Push and Pull mechanism to achieve bucket to bucket replication not working as expected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello All,

I am trying to achieve bucket to bucket replication using multisite sync policy configuration as per given exaples in ceph documentation.
I tried two scenarios::
Case- 1] Replication of objects from source bucket to target using "push" mechanism given in "EXAMPLE 6: SYNC TO DIFFERENT BUCKET" in https://docs.ceph.com/en/latest/radosgw/multisite-sync-policy/ document which did not worked.

Please guide me if I am missing something in case-1 (push mechanism) as its not working as expected.
Details are as follows:
source bucket name:: s-bucket
Destination bucket name:: d-bucket
Following is the sync group and pipe configuration on s-bucket  ::
[root@ssc-vm-g4-rhev4-1163 build]# ./bin/radosgw-admin sync policy get --bucket s-bucket
{
    "groups": [
        {
            "id": "s-default",
            "data_flow": {},
            "pipes": [
                {
                    "id": "pipe2",
                    "source": {
                        "bucket": "*",
                        "zones": [
                            "*"
                        ]
                    },
                    "dest": {
                        "bucket": "d-bucket",
                        "zones": [
                            "*"
                        ]
                    },
                    "params": {
                        "source": {
                            "filter": {
"tags": []
                            }
                        },
                        "dest": {},
                        "priority": 0,
                        "mode": "system",
                        "user": "testuser"
                    }
                }
            ],
            "status": "enabled"
        }
    ]
}


test1.txt object was copied to s-bucket which did not get replicated to d-bucket
[root@ssc-vm-g4-rhev4-1163 build]# aws s3 cp test1.txt s3://s-bucket  --endpoint http://10.230.247.71:8000
upload: ./test1.txt to s3://s-bucket/test1.txt
[root@ssc-vm-g4-rhev4-1163 build]# aws s3 ls  s3://s-bucket --endpoint http://10.230.247.71:8000
2022-03-16 02:29:09          6 test1.txt
[root@ssc-vm-g4-rhev4-1163 build]# aws s3 ls  s3://d-bucket --endpoint http://10.230.247.71:8001
[root@ssc-vm-g4-rhev4-1163 build]#

Tried by modifying source bucket name,source zone name and dest zone name in pipe2 but that also did not work.

Case- 2] Replication of objects from source bucket to target using "pull" mechanism given in "EXAMPLE 5: SYNC FROM A DIFFERENT BUCKET" in https://docs.ceph.com/en/latest/radosgw/multisite-sync-policy/ document. 
In this case if --dest-bucket is not given as stated in the this example then service gets crashed.
Following are the details:
source bucket:buck5
destination bucket: buck4
radosgw-admin sync group create --bucket=buck4 --group-id=buck4-default --status=enabled
radosgw-admin sync group pipe create --bucket=buck4 --group-id=buck4-default --pipe-id=pipe1 --source-zones=us-east --source-bucket=buck5 --dest-zones='*'

It worked only after giving --dest-bucket parameter in while creating pipe as follows:
radosgw-admin sync group pipe create --bucket=buck4 --group-id=buck4-default --pipe-id=pipe1 --source-zones=us-east --source-bucket=buck5 --dest-zones=us-south --dest-bucket=buck5
 Is this a bug?
Please guide me with both scenarios. 
P.S.: Tried this on latest versions of RADOS both on Quincy and Pacific.

Regards,
Shraddha Ghatol

Seagate Internal

_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx

[Index of Archives]     [CEPH Users]     [Ceph Devel]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux