Thanks for the warning, Eugen.
/Z
On Wed, 25 Oct 2023 at 13:04, Eugen Block wrote:
> Hi,
>
> this setting is not as harmless as I assumed. There seem to be more
> ticks/periods/health_checks involved. When I choose a mgr_tick_period
> value > 30 seconds the two MGRs keep respawning. 30 seconds
Hi,
this setting is not as harmless as I assumed. There seem to be more
ticks/periods/health_checks involved. When I choose a mgr_tick_period
value > 30 seconds the two MGRs keep respawning. 30 seconds are the
highest value that still seemed to work without MGR respawn, even with
increase
Thanks, Eugen. This is a useful setting.
/Z
On Thu, 19 Oct 2023 at 10:43, Eugen Block wrote:
> Hi,
>
> you can change the report interval with this config option (default 2
> seconds):
>
> $ ceph config get mgr mgr_tick_period
> 2
>
> $ ceph config set mgr mgr_tick_period 10
>
> Regards,
> Euge
Hi,
you can change the report interval with this config option (default 2
seconds):
$ ceph config get mgr mgr_tick_period
2
$ ceph config set mgr mgr_tick_period 10
Regards,
Eugen
Zitat von Chris Palmer :
I have just checked 2 quincy 17.2.6 clusters, and I see exactly the
same. The pgma
I have just checked 2 quincy 17.2.6 clusters, and I see exactly the
same. The pgmap version is bumping every two seconds (which ties in with
the frequency you observed). Both clusters are healthy with nothing
apart from client IO happening.
On 13/10/2023 12:09, Zakhar Kirpichenko wrote:
Hi,
