On 5/10/14 12:43 , Cédric Lemarchand wrote:
Hi Craig,
Thanks, I really appreciate the well detailed response.
I carefully note your advices, specifically about the CPU starvation
scenario, which as you said sounds scary.
About IO, datas will be very resilient, in case of crash, loosing not
fully written objects will not be a problem (they will be re uploaded
later), so I think in this specific case, disabling journaling could
be a way to improve IO.
How Ceph will handle that, are there caveats other than just loosing
objects that was in the data path when the crash occurs ? I know it
could sounds weird, but clients workflow could support such thing.
Thanks !
--
Cédric Lemarchand
Le 10 mai 2014 à 04:30, Craig Lewis <cle...@centraldesktop.com
<mailto:cle...@centraldesktop.com>> a écrit :
Disabling the journal does make sense in some cases, like all the data
is a backup copy.
I don't know anything about how Ceph behaves in that setup. Maybe
somebody else can chime in?
--
*Craig Lewis*
Senior Systems Engineer
Office +1.714.602.1309
Email cle...@centraldesktop.com <mailto:cle...@centraldesktop.com>
*Central Desktop. Work together in ways you never thought possible.*
Connect with us Website <http://www.centraldesktop.com/> | Twitter
<http://www.twitter.com/centraldesktop> | Facebook
<http://www.facebook.com/CentralDesktop> | LinkedIn
<http://www.linkedin.com/groups?gid=147417> | Blog
<http://cdblog.centraldesktop.com/>
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
