Swift Stat Timeout

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

 



Hey folks!

We have a user with ~1900 buckets in our RGW service and running this stat command results in a timeout for them:

swift -A https://<URL>:443/auth/1.0 -U <UID> -K <KEY> stat

Running the same command, but specifiying one of their buckets, returns promptly. Running the command for a different user with minimal buckets returns promptly as well. Turning up debug logging to 20
for rgw resulted in a great deal of logs showing:

20 reading from default.rgw.meta:root:.bucket.meta.<BUCKET-ID>
20 get_system_obj_state: rctx=0x559b32a6b570 obj=default.rgw.meta:root:.bucket.meta.<BUCKET-ID> state=0x559b32c37e40 s->prefetch_data=0
10 cache get: name=default.rgw.meta+root+.bucket.meta.<BUCKET-ID> : hit (requested=0x16, cached=0x17)
20 get_system_obj_state: s->obj_tag was set empty
10 cache get: name=default.rgw.meta+root+.bucket.meta.<BUCKET-ID> : hit (requested=0x11, cached=0x17)

Which looks like to me it is iterating getting the state of all their stuff. My question: is ~1900 an unreasonable amount of buckets such that we should expect to see this full account 'stat' command
timeout? Or should I be expecting it to return promptly still? Thanks!

Cheers,
Dylan
-- 
Dylan Griff
Senior System Administrator
CLE D063
RCS - Systems - University of Victoria
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux