Page MenuHomeSoftware Heritage

moma: Set the memory usage to the currently defined value
ClosedPublic

Authored by ardumont on Dec 8 2021, 4:25 PM.

Details

Summary

That will avoid flip-flop changes when puppet runs in moma. With the relative default of
5%, when puppet runs, the memcached memory configuration is updated, which restarts the
services and resets the cache (which disconnect users).

This commit settles on the current moma configuration so no disconnection should occur
when landed and applied.

Related to T3779

Test Plan
$ $SWH_PUPPET_ENVIRONMENT_HOME/bin/octocatalog-diff --octocatalog-diff-args --no-truncate-details --to staging moma
...
*** Running octocatalog-diff on host moma.softwareheritage.org
I, [2021-12-08T16:24:13.447812 #1144887]  INFO -- : Catalogs compiled for moma.softwareheritage.org
I, [2021-12-08T16:24:14.253619 #1144887]  INFO -- : Diffs computed for moma.softwareheritage.org
diff origin/production/moma.softwareheritage.org current/moma.softwareheritage.org
*******************************************
  File[/etc/memcached.conf] =>
   parameters =>
     content =>
      @@ -11,5 +11,5 @@
      _
       # Use <num> MB memory max to use for object storage.
      --m 1608
      +-m 1224
      _
      _
*******************************************
*** End octocatalog-diff on moma.softwareheritage.org

Diff Detail

Repository
rSPSITE puppet-swh-site
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

ardumont created this revision.
This revision is now accepted and ready to land.Dec 8 2021, 4:29 PM
vsellier added a subscriber: vsellier.

WDYT to put this value in production/common.yaml to also align webapp1 with this value ?

WDYT to put this value in production/common.yaml to also align webapp1 with this value ?

yeah, totally, ongoing change.

Adapt according to suggestion