On 02-04-2024 15:09, Zakhar Kirpichenko wrote:
Hi,
I'm adding a few OSDs to an existing cluster, the cluster is running with
`osd noout,noin`:
cluster:
id: 3f50555a-ae2a-11eb-a2fc-ffde44714d86
health: HEALTH_WARN
noout,noin flag(s) set
Specifically `noin` is
e : Zakhar Kirpichenko
Envoyé : jeudi 4 avril 2024 10:18
À : Eugen Block
Cc: ceph-users@ceph.io
Objet : [ceph-users] Re: Pacific 16.2.15 `osd noin`
Thank you, Eugen. This makes sense.
/Z
On Thu, 4 Apr 2024 at 10:32, Eugen Block wrote:
> Hi,
>
> the noin flag seems to be only applicable to
Thank you, Eugen. This makes sense.
/Z
On Thu, 4 Apr 2024 at 10:32, Eugen Block wrote:
> Hi,
>
> the noin flag seems to be only applicable to existing OSDs which are
> already in the crushmap. It doesn't apply to newly created OSDs, I
> could confirm that in a small test cluster with Pacific
Thanks, this is a good suggestion!
/Z
On Thu, 4 Apr 2024 at 10:29, Janne Johansson wrote:
> Den tors 4 apr. 2024 kl 06:11 skrev Zakhar Kirpichenko :
> > Any comments regarding `osd noin`, please?
> > >
> > > I'm adding a few OSDs to an existing cluster, the cluster is running
> with
> > > `osd
Hi,
the noin flag seems to be only applicable to existing OSDs which are
already in the crushmap. It doesn't apply to newly created OSDs, I
could confirm that in a small test cluster with Pacific and Reef. I
don't have any insights if that is by design or not, I assume it's
supposed to
Den tors 4 apr. 2024 kl 06:11 skrev Zakhar Kirpichenko :
> Any comments regarding `osd noin`, please?
> >
> > I'm adding a few OSDs to an existing cluster, the cluster is running with
> > `osd noout,noin`:
> >
> > cluster:
> > id: 3f50555a-ae2a-11eb-a2fc-ffde44714d86
> > health:
Any comments regarding `osd noin`, please?
/Z
On Tue, 2 Apr 2024 at 16:09, Zakhar Kirpichenko wrote:
> Hi,
>
> I'm adding a few OSDs to an existing cluster, the cluster is running with
> `osd noout,noin`:
>
> cluster:
> id: 3f50555a-ae2a-11eb-a2fc-ffde44714d86
> health:
