|
Hi Greg, Jonh, Zheng, CephFSers
Maybe a simple question but I think it is better to ask first than to complain after. We are currently undergoing an infrastructure migration. One of the first machines to go through this migration process is our standby-replay mds. We are running 10.2.2. My plan is to: - Shutdown the standby-replay mds - Re install it in 10.2.2 in a different host, reusing the same IP, keys and configurations. - Start the mds service I wasn't thinking this was problematic until I read: http://tracker.ceph.com/issues/17466 The issue mentioned above was started when the site admin added a new mds. He also did an (unintended) upgrade of the mds(es) from 10.2.1 to 10.2.3 but I am not sure if this is the reason of the problem. His mons started to fail because they got an invalid fscid, and the reason is some incoherent ordering of rank and fscid between the constructor and the struct. I just want to be sure that I won't hit a similar issue: - In what exact circumstances is this problem triggered? - Is it triggered when you add a brand new standby-replay mds (new IP, new key)? I am hopping that in my case, I shouldn't be affected. TIA Goncalo |
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
