Re: Ceph mon crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday, March 20, 2012 at 1:02 AM, ruslan usifov wrote:
> I found it in source. I want to liquidate of war messages which appear
> when i monitor cluster with follow:
> 
> ceph -w
> 
> There was messages that i have one down mds (actually i doesn't have any)
Ah. I'm not sure we actually support removal of all the MDSes once you start one up. Given the prevalence of RBD users we probably should, though! Bug filed: http://tracker.newdream.net/issues/2195


I *think* that if you don't ever create an MDS that line won't show up; somebody who runs an RBD cluster could tell you for sure. :)
> 
> > If necessary I can figure out how to create a good MDSMap and inject it into your monitors, but I'd rather not if you don't have any data in there. (In which case, reformat the cluster.)
> 
> This is a test environment, so i reformat cluster map manually. Also i
> must say that mons die not immediately when i run (ceph mds rm 1), but
> after some time

Yes, when you ran the mds rm command you corrupted your MDSMap, but the system doesn't notice right away since the map is not being accessed by clients or your servers. But eventually you (or a monitoring service, more likely) ran the ceph health command, which made the mon look at the MDSMap, which caused an assert. Then the ceph tool tried again on a different monitor, etc.



-Greg 

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux