http://tracker.ceph.com/issues/9206
My post to the ML: http://www.spinics.net/lists/ceph-users/msg12665.html
IIRC, the system uses didn't see the other user's bucket in a bucket listing, but they could read and write the objects fine.
On Wed, Nov 12, 2014 at 11:16 AM, Aaron Bassett <aaron@xxxxxxxxxxxxxxxxx> wrote:
In playing around with this a bit more, I noticed that the two users on the secondary node cant see each others buckets. Is this a problem?
IIRC, the system user couldn't see each other's buckets, but they could read and write the objects.
Do you have a link to that bug#? I want to see if it gives me any clues.On Nov 11, 2014, at 6:56 PM, Craig Lewis <clewis@xxxxxxxxxxxxxxxxxx> wrote:It is apache 2.4, but I’m actually running 0.80.7 so I probably have that bug fix?I see you're running 0.80.5. Are you using Apache 2.4? There is a known issue with Apache 2.4 on the primary and replication. It's fixed, just waiting for the next firefly release. Although, that causes 40x errors with Apache 2.4, not 500 errors.No, the unreleased 0.80.8 has the fix.Yes I can write everywhere and radosgw-agent isn’t getting any 403s like it was earlier when I had mismatched keys. The .us-nh.rgw.buckets.index pool is syncing properly, as are the users. It seems like really the only thing that isn’t syncing is the .zone.rgw.buckets pool.Have you verified that both system users can read and write to both clusters? (Just make sure you clean up the writes to the slave cluster).That's pretty much the same behavior I was seeing with Apache 2.4.Try downgrading the primary cluster to Apache 2.2. In my testing, the secondary cluster could run 2.2 or 2.4.Aaron
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
