On Tue, Apr 24, 2018 at 11:50 AM, Marc Haber < mh+debian-packa...@zugschlus.de> wrote:
> severity #896767 normal > tags #896767 confirmed upstream > thanks > > On Tue, Apr 24, 2018 at 08:18:44AM +0000, Manuel Arostegui wrote: > > Context: Running a baremetal server with 512GB RAM + 10 SSDs disks + 16 > > Cores + MariaDB 10.1 > > This database is part of a farm, with other 2 hosts (which are running > > Debian 8) > > This is a big big big machine that will need serious tweaking from the > default values anyway. > > I think that running with -R is the correct way to do things for the > vast majory of installations. > The main issue is that that -R is a new option has been enabled by default from Debian 8 to Debian 9. I agree that this host isn't an standard host in most of the installations, but enabling such new option by default from one version to another can cause service degradation while upgrading from Jessie to Stretch, which is a regression on how atop works. The options atop runs with by default on Jessie (-a and -w) are still available on the atop version shipped with Stretch, so it can be just started like that too. > > I do agree that having -R as non-configurable default is suboptimal > though. I have filed a PR upstream making this setting configurable from > /etc/default/atop. > > As a local workaround, please edit /usr/share/atop/atop.daily and remove > the -R option from the atop call in the last line. > That was done to verify the issue. And it has been left like that on the host for now. However, we might need to stop atop across the fleet as this might happen in other hosts too once they get to Stretch. Thanks Manuel.
