Ok, thank you guys
The version is 10.2.10
Matteo
> Il giorno 20 nov 2017, alle ore 23:15, Christian Balzer ha
> scritto:
>
> On Mon, 20 Nov 2017 10:35:36 -0800 Chris Taylor wrote:
>
>> On 2017-11-20 3:39 am, Matteo Dacrema wrote:
>>> Yes I mean the existing Cluster.
>>> SSDs
On Mon, 20 Nov 2017 10:35:36 -0800 Chris Taylor wrote:
> On 2017-11-20 3:39 am, Matteo Dacrema wrote:
> > Yes I mean the existing Cluster.
> > SSDs are on a fully separate pool.
> > Cluster is not busy during recovery and deep scrubs but I think it’s
> > better to limit replication in some way
On 2017-11-20 3:39 am, Matteo Dacrema wrote:
Yes I mean the existing Cluster.
SSDs are on a fully separate pool.
Cluster is not busy during recovery and deep scrubs but I think it’s
better to limit replication in some way when switching to replica 3.
My question is to understand if I need to
Yes I mean the existing Cluster.
SSDs are on a fully separate pool.
Cluster is not busy during recovery and deep scrubs but I think it’s better to
limit replication in some way when switching to replica 3.
My question is to understand if I need to set some options parameters to limit
the impact
Hello,
On Mon, 20 Nov 2017 11:56:31 +0100 Matteo Dacrema wrote:
> Hi,
>
> I need to switch a cluster of over 200 OSDs from replica 2 to replica 3
I presume this means the existing cluster and not adding 100 OSDs...
> There are two different crush maps for HDD and SSDs also mapped to two
>
> Op 20 november 2017 om 11:56 schreef Matteo Dacrema :
>
>
> Hi,
>
> I need to switch a cluster of over 200 OSDs from replica 2 to replica 3
> There are two different crush maps for HDD and SSDs also mapped to two
> different pools.
>
> Is there a best practice to use?
Hi,
I need to switch a cluster of over 200 OSDs from replica 2 to replica 3
There are two different crush maps for HDD and SSDs also mapped to two
different pools.
Is there a best practice to use? Can this provoke troubles?
Thank you
Matteo
___