Hi Yehuda,
Can you help to review the latest patch with throttle mechanism you suggested.
Thanks!
Thanks,
Guang
On Aug 4, 2014, at 3:20 PM, Guang Yang yguan...@outlook.com wrote:
Hi Yehuda,
Here is the new pull request - https://github.com/ceph/ceph/pull/2187
Thanks,
Guang
On Jul 31,
Hi Yehuda,
Can I please get any suggestion on the get bucket_location API
error? Please share any info, which can help us to debug more here.
Thanks
Swami
On Mon, Aug 4, 2014 at 4:44 PM, M Ranga Swami Reddy
swamire...@gmail.com wrote:
Hi Yehuda,
I tried to test the get bucket location API,
At the moment we don't support this api call. Adding it should be
pretty easy, and it's definitely something that could be done with the
help of a willing community member.
Yehuda
On Tue, Aug 12, 2014 at 9:58 AM, M Ranga Swami Reddy
swamire...@gmail.com wrote:
Hi Yehuda,
Can I please get any
Thanks Yehuda. I am testing the S3 APIs suing the openstack+ceph.
Could able test a couple of APIs like put/get/delete bucket (using the
boto python libraries). When I tried for get bucket location I got an
error mentioned in my previous email.
And explored the ceph source code and not able see
This stable update release for Dumpling includes primarily fixes for RGW,
including several issues with bucket listings and a potential data
corruption problem when multiple multi-part uploads race. There is also
some throttling capability added in the OSD for scrub that can mitigate
the
Sage, if I understood you correctly on the video call, you have
reservations about making libcommon a dynamic library because of
incompatible changes between versions causing problems when packages
use different versions, and you brought up the idea of having a static
version and a dynamic
On Tue, 12 Aug 2014, Adam Crume wrote:
Sage, if I understood you correctly on the video call, you have
reservations about making libcommon a dynamic library because of
incompatible changes between versions causing problems when packages
use different versions, and you brought up the idea of
The Mutex tracepoints were just a driving example, so definitely feel
free to remove them. But libcommon is pretty big, so I suspect that
that if tracing is merged that someone will eventually want
tracepoints in libcommon.
On Tue, Aug 12, 2014 at 12:41 PM, Adam Crume adamcr...@gmail.com wrote:
Hi Sage,
I set up a simple virtual cluster to test this today, and it appears
that all is well. The issue I was attempting to fix doesn't appear to
be present in wip-firefly-dmcrypt's ceph-disk.
Steve
On Tue, Aug 12, 2014 at 10:39 AM, Sage Weil s...@inktank.com wrote:
Hi Steve,
We ran into a
With the version match requirements, I think it would work. Will
automake and libtool let us have a static and dynamic version of the
same library, or would we have two similarly-named libraries?
Removing the tracepoints from libcommon would be an appropriate short
term fix. Besides just this,
On Tue, 12 Aug 2014, Steve Taylor wrote:
Hi Sage,
I set up a simple virtual cluster to test this today, and it appears
that all is well. The issue I was attempting to fix doesn't appear to
be present in wip-firefly-dmcrypt's ceph-disk.
Great. Thanks for testing!
sage
Steve
On
Hey Alfredo,
Can you take a look at these ceph-disk changes?
https://github.com/ceph/ceph/pull/2247
The first few you saw yesterday, but the last few fix up ceph-disk list to
do something useful when dmcrypt is used...
Thanks!
sage
--
To unsubscribe from this list: send the line
On 08/11/2014 07:50 PM, Haomai Wang wrote:
Hi Sage, Josh:
ImageIndex is aimed to hold each object's location info which avoid
extra checking for none-existing object. It's only used when image flags
exists LIBRBD_CREATE_NONSHARED. Otherwise, ImageIndex will become gawp and
has no effect.
I
13 matches
Mail list logo