Re: Dual network board setup info

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

 



Em qui., 28 de nov. de 2019 às 18:32, Rodrigo Severo - Fábrica
<rodrigo@xxxxxxxxxxxxxxxxxxx> escreveu:
>
> Em qui., 28 de nov. de 2019 às 13:39, Wido den Hollander
> <wido@xxxxxxxx> escreveu:
> >
> > On 11/28/19 5:23 PM, Rodrigo Severo - Fábrica wrote:
> > > Em qui., 28 de nov. de 2019 às 00:34, Konstantin Shalygin
> > > <k0ste@xxxxxxxx> escreveu:
> > >>
> > >>> My servers have 2 network boards each. I would like to use the current
> > >>> local one to talk to Cephs clients (both CephFS and Object Storage)
> > >>> and use the second one to all Cephs processes to talk one to the
> > >>> other.
> > >>>
> > >>
> > >> Ceph support `cluster network` and `public network` options. Only OSD
> > >> work with cluster network. Any other is a OSD clients - public network.
> > >
> > > Great. How do I migrate from my current single network board to a dual one?
> > >
> > > Can I migrate servers one by one to the dual network setup or do I
> > > have to stop the whole ceph cluster and restart it all already on the
> > > dual setup?
> >
> > Set the cluster_network in the ceph.conf and restart the OSDs one by one.
>
> Just tried that. The first OSD that I'm trying to restart won't came
> up again.

Does anybody has any suggestion on how to get my ceph fs back to healthy status?

I'm even considering stop it all and restarting but I'm afraid it
won't come back up with the new config.

Ideias? Suggestions?


Rodrigo


It presents the following messages which aren't that useful
> to me:
>
> Nov 28 18:26:33 a2-df systemd[1]: ceph-osd@1.service: Start request
> repeated too quickly.
> Nov 28 18:26:33 a2-df systemd[1]: ceph-osd@1.service: Failed with
> result 'exit-code'.
> Nov 28 18:26:33 a2-df systemd[1]: Failed to start Ceph object storage
> daemon osd.1.
> -- Subject: Unit ceph-osd@1.service has failed
> -- Defined-By: systemd
> -- Support: http://www.ubuntu.com/support
> --
> -- Unit ceph-osd@1.service has failed.
> --
> -- The result is RESULT.
>
> I also see the following error messages:
> Nov 28 18:26:46 a2-df ceph-mon[2526]: 2019-11-28 18:26:46.230
> 7f487dee1700 -1 set_mon_vals failed to set cluster_network =
> 192.168.111.0/24: Configuration option 'cluster_network' may not be
> modified at runtime
> Nov 28 18:26:46 a2-df ceph-mon[2526]: 2019-11-28 18:26:46.230
> 7f487dee1700 -1 set_mon_vals failed to set public_network =
> 192.168.109.0/24: Configuration option 'public_network' may not be
> modified at runtime
>
> There are 2 things that I don't understand in these messages:
>
> 1. Why is it mentioning configuration option 'public_network' in these
> error messages as I didn't change the public_network config, I only
> added a cluster_network one?
>
> 2. Why are there messages from ceph-mon when I'm trying to restart ceph-osd?
>
> And the most important issue: how can I get my osd back online?
>
>
> Regards,
>
> Rodrigo
_______________________________________________
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