Hi buddies,
I am doing investigation on Ceph and Swift,and I am newbie to Ceph.
I am unclear to the behaviour of the Ceph when there is overload situation.
According to the doc, when Ceph do CRUSH, if it find the OSD is overload,
it will skip it to select the other OSD. It means if the OSD
On 06/06/2014 10:14 AM, zou wonder wrote:
Hi buddies,
I am doing investigation on Ceph and Swift,and I am newbie to Ceph.
I am unclear to the behaviour of the Ceph when there is overload situation.
According to the doc, when Ceph do CRUSH, if it find the OSD is overload,
it will skip it to
Hi Wido:
Thanks for your kindness, i checked the codes just now, seems there
were no overload related thing in CRUSH codes. It is a little bit not
consistent with the CRUSH paper.
So if the %100 utilized OSD is returned, the objects will still be
written on the underlined storage device?
How
On 06/06/2014 11:27 AM, zou wonder wrote:
Hi Wido:
Thanks for your kindness, i checked the codes just now, seems there
were no overload related thing in CRUSH codes. It is a little bit not
consistent with the CRUSH paper.
So if the %100 utilized OSD is returned, the objects will still be
Hi Loic,
the basic implementation looks very clean.
I have few comments/ideas:
- the reconstruction strategy using the three levels is certainly efficient
enough for standard cases but does not guarantee always the minimum decoding
(in cases where one layer is not enough to reconstruct) since
Hi Yehuda,
Can you take a look at a very high level of the code change, here is the pull
request - https://github.com/ceph/ceph/pull/1929.
If things look good to you, i will continue the effort and make it more
clear/complete by end of next week.
Thanks,
Guang
On Jun 2, 2014, at 9:37 PM,
Hi all.
Sorry for a rude offtop, but looks like nobody can help me at ceph-users.
Here is the link to my email:
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2014-June/040383.html
Here some additional data:
http://pastebin.com/Nc4y3S1U
During read requests i can see in logs:
2014-06-06
Hi Andreas,
On 06/06/2014 13:46, Andreas Joachim Peters wrote: Hi Loic,
the basic implementation looks very clean.
I have few comments/ideas:
- the reconstruction strategy using the three levels is certainly efficient
enough for standard cases but does not guarantee always the minimum
[Moving to ceph-devel]
Try putting debug ms = 1 and debug objecter = 20 in your ceph.conf under
[clients] and see if the request is getting sent, and whether the reply is
coming back.
sage
On Fri, 6 Jun 2014, Leo Chen wrote:
hi sage,I use rados_stat() in fuse module , It's block all all
On Fri, 6 Jun 2014, zou wonder wrote:
Hi Wido:
Thanks for your kindness, i checked the codes just now, seems there
were no overload related thing in CRUSH codes. It is a little bit not
consistent with the CRUSH paper.
So if the %100 utilized OSD is returned, the objects will still be
---BeginMessage---
Hi,
Please find the latest report on new defect(s) introduced to ceph found with
Coverity Scan.
Defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)
** CID 1220854: Invalid iterator comparison (MISMATCHED_ITERATOR)
/osd/PG.cc: 981 in
On Fri, 6 Jun 2014, Alexey Kurnosov wrote:
Hi all.
Sorry for a rude offtop, but looks like nobody can help me at ceph-users.
Here is the link to my email:
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2014-June/040383.html
Here some additional data:
http://pastebin.com/Nc4y3S1U
Hi Greg,
I have found the reason. user.cephos.spill_out can't be apply to new
object when calling clone method. So if the origin object is spill
out, the new object still has no spill out marker.
I pushed a commit (https://github.com/ceph/ceph/pull/1932) to help
cover this situation.
On Tue,
The fix should make clone method copy cephos prefix xattrs
On Sat, Jun 7, 2014 at 2:54 AM, Haomai Wang haomaiw...@gmail.com wrote:
Hi Greg,
I have found the reason. user.cephos.spill_out can't be apply to new
object when calling clone method. So if the origin object is spill
out, the new
On Fri, Jun 6, 2014 at 11:55 AM, Haomai Wang haomaiw...@gmail.com wrote:
The fix should make clone method copy cephos prefix xattrs
On Sat, Jun 7, 2014 at 2:54 AM, Haomai Wang haomaiw...@gmail.com wrote:
Hi Greg,
I have found the reason. user.cephos.spill_out can't be apply to new
object
Yes, maybe you can add it in your branch. Because it will happen when
creating object and set spill out
On Sat, Jun 7, 2014 at 2:59 AM, Gregory Farnum g...@inktank.com wrote:
On Fri, Jun 6, 2014 at 11:55 AM, Haomai Wang haomaiw...@gmail.com wrote:
The fix should make clone method copy cephos
On Fri, Jun 06, 2014 at 08:57:46AM -0700, Sage Weil wrote:
On Fri, 6 Jun 2014, Alexey Kurnosov wrote:
Hi all.
Sorry for a rude offtop, but looks like nobody can help me at ceph-users.
Here is the link to my email:
Hello,
I am pleased to announce an alpha version of the Ceph Wireshark
Dissector. As some you you may know I am working on this dissector as a
GSOC project this summer. I have gotten some initial work completed and
wanted to share in case someone finds it useful.
So far the dissector can parse
(sorry if this is a dupe, sendmail issues)
Hey Cephers,
If you still haven?t signed up for Ceph Day Boston you should stop
procrastinating and proceed directly to the event page! :)
http://www.inktank.com/cephdays/boston/
We?d really love to have all of our closest Ceph friends join us for
19 matches
Mail list logo
