rest-bench always fails on initial execution
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ceph (Ubuntu) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
prompt> rest-bench --access-key=xxx --secret=yyy --api-host=
host=localhost
ERROR: failed to create bucket: ConnectionFailed
failed initializing benchmark
Except from apache2 access.log;
127.0.0.1 - - [05/Sep/
Excerpt from radosgw log file:
2012-09-05 12:40:38.448014 7f5068fc9700 10 cache get: name=.users+
2012-09-05 12:40:38.448069 7f5068fc9700 10 get_canon_
2012-09-05 12:40:38.448075 7f5068fc9700 10 auth_hdr:
PUT
x-amz-date:Wed, 05 Sep 2012 11:40:38 GMT
/rest-bench-bucket/
2012-09-05 12:40:38.448187 7f5068fc9700 15 b64=skwbg2pHJMb
2012-09-05 12:40:38.448193 7f5068fc9700 15 auth_sign=
2012-09-05 12:40:38.448196 7f5068fc9700 15 compare=0
2012-09-05 12:40:38.448201 7f5068fc9700 2 req 1:0.001795:s3:PUT /rest-bench-
2012-09-05 12:40:38.448207 7f5068fc9700 2 req 1:0.001801:s3:PUT /rest-bench-
2012-09-05 12:40:38.448872 7f5068fc9700 2 req 1:0.002466:s3:PUT /rest-bench-
2012-09-05 12:40:38.448888 7f5068fc9700 10 --> Status: 100
2012-09-05 12:40:38.448927 7f5068fc9700 2 req 1:0.002521:s3:PUT /rest-bench-
2012-09-05 12:40:38.448966 7f5068fc9700 20 get_obj_state: rctx=0x7f50a8002160 obj=.rgw:
2012-09-05 12:40:38.448975 7f5068fc9700 10 cache get: name=.rgw+
2012-09-05 12:40:38.449498 7f5068fc9700 10 cache put: name=.rgw+
2012-09-05 12:40:38.449505 7f5068fc9700 10 adding .rgw+rest-
2012-09-05 12:40:38.449538 7f5068fc9700 20 get_obj_state: rctx=0x7f50a8008fa0 obj=.rgw:
2012-09-05 12:40:38.449546 7f5068fc9700 10 cache get: name=.rgw+
2012-09-05 12:40:38.450015 7f5068fc9700 10 cache put: name=.rgw+
2012-09-05 12:40:38.450020 7f5068fc9700 10 adding .rgw+.pools.avail to cache LRU end
2012-09-05 12:40:38.778331 7f5068fc9700 15 omap_set bucket=.rgw oid=.pools.avail key=.rgw.buckets
2012-09-05 12:40:39.223706 7f5068fc9700 10 cache put: name=.rgw+
2012-09-05 12:40:39.223718 7f5068fc9700 10 moving .rgw+.pools.avail to cache LRU end
2012-09-05 12:40:39.223744 7f5068fc9700 10 distributing notification oid=notify bl.length()=174
2012-09-05 12:40:39.224468 7f50c8887700 10 RGWWatcher:
2012-09-05 12:40:39.224489 7f50c8887700 10 cache put: name=.rgw+
2012-09-05 12:40:39.224494 7f50c8887700 10 moving .rgw+.pools.avail to cache LRU end
2012-09-05 12:40:40.454025 7f5068fc9700 10 cache put: name=.rgw+
2012-09-05 12:40:40.454034 7f5068fc9700 10 moving .rgw+rest-
2012-09-05 12:40:40.454038 7f5068fc9700 10 updating xattr: name=user.rgw.acl bl.length()=143
2012-09-05 12:40:40.454067 7f5068fc9700 10 distributing notification oid=notify bl.length()=406
2012-09-05 12:40:40.454835 7f50c8887700 10 RGWWatcher:
2012-09-05 12:40:40.454855 7f50c8887700 10 cache put: name=.rgw+
2012-09-05 12:40:40.454859 7f50c8887700 10 moving .rgw+rest-
2012-09-05 12:40:40.454863 7f50c8887700 10 updating xattr: name=user.rgw.acl bl.length()=143
2012-09-05 12:40:40.455346 7f5068fc9700 20 store_bucket_info: bucket=
2012-09-05 12:40:40.455357 7f5068fc9700 20 rgw_create_bucket returned ret=0 bucket=
2012-09-05 12:40:40.455372 7f5068fc9700 15 omap_set bucket=.users.uid oid=ubuntu.buckets key=rest-
2012-09-05 12:40:40.537346 7f5068fc9700 10 --> Status: 200
2012-09-05 12:40:40.537357 7f5068fc9700 10 --> Content-type: application/xml^M
2012-09-05 12:40:40.891583 7f5068fc9700 2 req 1:2.445176:s3:PUT /rest-bench-
2012-09-05 12:40:40.891736 7f5068fc9700 1 ====== req done req=0x7f50d634fe20 http_status=200 ======
rest-bench-bucket also shows up in a 's3 list' output as well.
Subsequent runs of rest-bench work just fine - its just the initial one that fails.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: rest-bench 0.48.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-12-generic x86_64
ApportVersion: 2.5.1-0ubuntu3
Architecture: amd64
Date: Wed Sep 5 12:41:28 2012
SourcePackage: ceph
UpgradeStatus: No upgrade log present (probably fresh install)
This is actually just a timeout on the initial hit on the radow gateway - it takes a few seconds to initialize the rados pools.
Marking 'Low' and 'Triaged'; increasing the timeout in rest-bench is probably the correct way to resolve this issue.