|
In my case I am using SCST, so that is what my experience is based on. For our VMware we are using NFS, but for Hyper-V and Solaris we are using iSCSI. There is actually some work done to make userland SCST which could be interesting for making a scst_librbd integration that bypasses the need for krbd. From: Nick Fisk [mailto:nick@xxxxxxxxxx]
I assume Brady is referring to the death spiral LIO gets into with some initiators, including vmware, if an IO takes longer than about 10s. I haven’t heard of
anything, and can’t see any changes, so I would assume this issue still remains. I would look at either SCST or NFS for now. From: ceph-users [mailto:ceph-users-bounces@xxxxxxxxxxxxxx]
On Behalf Of Adrian Saul I am not sure if there is a hard and fast rule you are after, but pretty much anything that would cause ceph transactions to be blocked (flapping OSD, network
loss, hung host) has the potential to block RBD IO which would cause your iSCSI LUNs to become unresponsive for that period. For the most part though, once that condition clears things keep working, so its not like a hang where you need to reboot to clear it. Some situations we have
hit with our setup:
-
Failed OSDs (dead disks) – no issues
-
Cluster rebalancing – ok if throttled back to keep service times down
-
Network packet loss (bad fibre) – painful, broken communication everywhere, caused a krbd hang needing a reboot
-
RBD Snapshot deletion – disk latency through roof, cluster unresponsive for minutes at a time, won’t do again. From: ceph-users [mailto:ceph-users-bounces@xxxxxxxxxxxxxx]
On Behalf Of Brady Deetz I apologize if this is a duplicate of something recent, but I'm not finding much. Does the issue still exist where dropping an OSD results in a LUN's I/O hanging? I'm attempting to determine if I have to move off of VMWare in order to safely use Ceph as my VM storage. Confidentiality: This email and any attachments are confidential and may be subject to copyright, legal or some other professional privilege. They are intended solely for the attention and use of the named addressee(s). They may only be
copied, distributed or disclosed with the consent of the copyright owner. If you have received this email by mistake or by breach of the confidentiality clause, please notify the sender immediately by return email and delete or destroy all copies of the email.
Any confidentiality, privilege or copyright is not waived or lost because this email has been sent to you by mistake.
|
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
