Re: Monitor recovery

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

 



Thank you Martin! I am familiar with that process, I just didn’t understand that the monmap was the only difference between the monitor databases. This makes sense if Paxos is maintaining the full DB synchronization, but the structure and contents of the database were not clear. I have discovered in this process I would like to understand more about the exact contents of it, although I assume it’s nothing outside what is available in the CLI. (In studying this, I may learn more about the CLI!! :-))

The aspect that leads me to believe I need to learn more is after doing this, I have lost cephfs subvolume mappings. Do I potentially need to do the same kind of thing with the MDS stores (obviously leaving out the monmap changes).

Thank you! Brian

> On Oct 10, 2020, at 6:56 AM, Martin Verges <martin.verges@xxxxxxxx> wrote:
> 
> Hello Brian,
> 
> as long as you have at least one working MON, it's kind of easy to recover. Shutdown all MONs, modify the MONMAP by hand, leaving just one of the working MONs and then start it up. After that, redeploy the other mons to have your quorum and redundancy back again.
> 
> You find more details and commands at https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/#recovering-a-monitor-s-broken-monmap <https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/#recovering-a-monitor-s-broken-monmap>.
> 
> --
> Martin Verges
> Managing director
> 
> Mobile: +49 174 9335695
> E-Mail: martin.verges@xxxxxxxx <mailto:martin.verges@xxxxxxxx>
> Chat: https://t.me/MartinVerges <https://t.me/MartinVerges>
> 
> croit GmbH, Freseniusstr. 31h, 81247 Munich
> CEO: Martin Verges - VAT-ID: DE310638492
> Com. register: Amtsgericht Munich HRB 231263
> 
> Web: https://croit.io <https://croit.io/>
> YouTube: https://goo.gl/PGE1Bx <https://goo.gl/PGE1Bx>
> 
> 
> Am Sa., 10. Okt. 2020 um 07:16 Uhr schrieb Brian Topping <brian.topping@xxxxxxxxx <mailto:brian.topping@xxxxxxxxx>>:
> Hello experts,
> 
> I have accidentally created a situation where the only monitor in a cluster has been moved to a new node without it’s /var/lib/ceph contents. Not realizing what I had done, I decommissioned the original node, but still have the contents of it’s /var/lib/ceph. 
> 
> Can I shut down the monitor running on the new node, copy monitor data from the original node to the new node and restart the monitor? Or is there information in the monitor database that is tied to the original node? If that’s the case, I suspect I need to somehow recommission the original node.
> 
> Thanks for any feedback on this situation!
> 
> Brian
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx <mailto:ceph-users@xxxxxxx>
> To unsubscribe send an email to ceph-users-leave@xxxxxxx <mailto:ceph-users-leave@xxxxxxx>

_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux