Ceph » rgw

It's not uncommon for the system users in a sync relationship to use the same keys. If this occurs, every metadata sync will return a 409 when attempting to sync that user due to the keys from the user on the source side will collide with the (same) keys of the existing system user on the destination side.

We could either account for this in the sync agent code and treat it as not an error or we could tweak the RGW code to allow collisions for system users.

Here is a snippet from the RGW logs on the sync destination side.

PUT

application/json; charset=UTF-8
Thu, 29 Aug 2013 18:55:24 GMT
/admin/metadata/user
2013-08-29 11:55:24.484289 7fb6187f8700 15 calculated digest=8FSYjAGlHytvzKKB1hMeBZQJeng=
2013-08-29 11:55:24.484291 7fb6187f8700 15 auth_sign=8FSYjAGlHytvzKKB1hMeBZQJeng=
2013-08-29 11:55:24.484293 7fb6187f8700 15 compare=0
2013-08-29 11:55:24.484294 7fb6187f8700 20 system request
2013-08-29 11:55:24.484297 7fb6187f8700 2 req 65:0.000323::PUT /admin/metadata/user:set_metadata:reading permissions
2013-08-29 11:55:24.484302 7fb6187f8700 2 req 65:0.000328::PUT /admin/metadata/user:set_metadata:verifying op mask
2013-08-29 11:55:24.484305 7fb6187f8700 20 required_mask= 0 user.op_mask=7
2013-08-29 11:55:24.484306 7fb6187f8700 2 req 65:0.000332::PUT /admin/metadata/user:set_metadata:verifying op permissions
2013-08-29 11:55:24.484310 7fb6187f8700 2 overriding permissions due to system operation
2013-08-29 11:55:24.484311 7fb6187f8700 2 req 65:0.000337::PUT /admin/metadata/user:set_metadata:verifying op params
2013-08-29 11:55:24.484314 7fb6187f8700 2 req 65:0.000340::PUT /admin/metadata/user:set_metadata:executing
2013-08-29 11:55:24.484680 7fb6187f8700 20 get_obj_state: rctx=0x7fb5bc007540 obj=.users.uid.1:client0-system-user state=0x7fb5bc0091e8 s->prefetch_data=0
2013-08-29 11:55:24.484690 7fb6187f8700 10 cache get: name=.users.uid.1+client0-system-user : miss
2013-08-29 11:55:24.486392 7fb6187f8700 10 cache put: name=.users.uid.1+client0-system-user
2013-08-29 11:55:24.486414 7fb6187f8700 10 adding .users.uid.1+client0-system-user to cache LRU end
2013-08-29 11:55:24.486440 7fb6187f8700 20 get_obj_state: rctx=0x7fb5bc007540 obj=.users.1:1te6NH5mcdcq0Tc5i8i3 state=0x7fb5bc006d68 s->prefetch_data=0
2013-08-29 11:55:24.486454 7fb6187f8700 10 moving .users.1+1te6NH5mcdcq0Tc5i8i3 to cache LRU end
2013-08-29 11:55:24.486456 7fb6187f8700 10 cache get: name=.users.1+1te6NH5mcdcq0Tc5i8i3 : hit
2013-08-29 11:55:24.486462 7fb6187f8700 20 get_obj_state: s->obj_tag was set empty
2013-08-29 11:55:24.486468 7fb6187f8700 10 moving .users.1+1te6NH5mcdcq0Tc5i8i3 to cache LRU end
2013-08-29 11:55:24.486470 7fb6187f8700 10 cache get: name=.users.1+1te6NH5mcdcq0Tc5i8i3 : hit
2013-08-29 11:55:24.486492 7fb6187f8700 20 get_obj_state: rctx=0x7fb5bc007540 obj=.users.uid.1:client1-system-user state=0x7fb5bc00d158 s->prefetch_data=0
2013-08-29 11:55:24.486500 7fb6187f8700 10 moving .users.uid.1+client1-system-user to cache LRU end
2013-08-29 11:55:24.486502 7fb6187f8700 10 cache get: name=.users.uid.1+client1-system-user : hit
2013-08-29 11:55:24.486506 7fb6187f8700 20 get_obj_state: s->obj_tag was set empty
2013-08-29 11:55:24.486511 7fb6187f8700 10 moving .users.uid.1+client1-system-user to cache LRU end
2013-08-29 11:55:24.486513 7fb6187f8700 10 cache get: name=.users.uid.1+client1-system-user : hit
2013-08-29 11:55:24.486532 7fb6187f8700 0 WARNING: can't store user info, access key already mapped to another user
2013-08-29 11:55:24.486556 7fb6187f8700 5 ERROR: can't put key: (17) File exists
2013-08-29 11:55:24.486592 7fb6187f8700 2 req 65:0.002618::PUT /admin/metadata/user:set_metadata:http status=409