On Tue, Apr 24, 2018 at 12:16 PM, Marc Haber < [email protected]> wrote:
> On Tue, Apr 24, 2018 at 12:06:22PM +0200, Manuel Arostegui wrote: > > On Tue, Apr 24, 2018 at 11:50 AM, Marc Haber < > > [email protected]> 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. > > This is an upstream change from 1.26 to 2.2.6. I am sure that 2.2.6 in > stretch behaves differently from 1.26 in jessie in a gazillion of > places. > May be. However, starting atop with the same old command line options results in no damage to a Debian 9 system, whereas the new one does, and quite heavily as it has been shown. The reality is that installing atop caused a production outage, which could have been prevented if the new option wasn't used by default. I am not blaming the debian package here! :-) > > However, we might need to stop atop across the fleet as this might happen > > in other hosts too once they get > > to Stretch. > > This won't be changing in Debian's stable release anyway, since this is > not a serious bug. > > And sorry, I won't divert from upstream's defaults here. > > I am also following upstream's discussion. But if it is decided not to change the default start up options and "-R" is kept, I would strongly suggest not to use it by default whilst installing the debian package - it caused production issues. Thanks! Manuel.
