All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: [DRBD-announce] linstor-proxmox v5.1.6
Date: Thu, 17 Jun 2021 15:06:15 +0200	[thread overview]
Message-ID: <20210617130615.GP1398@rck.sh> (raw)

Dear DRBD on Proxmox users,

This is version 5.1.6 of the PVE Plugin for LINSTOR.

If you are satisfied with your current cluster, you don't need to update.

Quoting the commit message that triggered that release:

Proxmox queries the status of all storages every few seconds. There is a cache
they pass in, but that only makes sense for multiple storages of one storage
type (i.e., 'drbd'). One can then use that passed in cache for a "query loop"
of all storages of that particular type. That helps, but still the plugin's
status function gets called every few seconds with a cold cache.

On large clusters (~10 nodes, a few hundred resources), executing the
expensive "storage-pool list" query in LINSTOR every few seconds on all nodes
saturates the LINSTOR REST-API/controller and the cluster becomes
slow/unusable.

As the plugin gets instantiated over and over again, it is not possible to keep
a "plugin global" cache, so moving the cache to the file system looks like a
good fit.

The new option 'statuscache' can be set to a positive number of seconds and
will then keep a status cache (currently only the storage pools) for that
number of seconds. If one wants to make use of this, the option has to be set
on *all* drbd storages in /etc/pve/storage.cfg.

The cache is written to the file system in /var/cache/linstor-proxmox/. Just
having the cache and using it was good enough to fix that particular customer's
issues. You also might want to use a tmpfs for that directory, but that is up
to you.

GIT: https://github.com/LINBIT/linstor-proxmox/commit/b337aa846bcb526cc384dd588e6026b61dffcac1
TGZ: https://pkg.linbit.com//downloads/connectors/linstor-proxmox-5.1.6.tar.gz

Regards, rck

                 reply	other threads:[~2021-06-17 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210617130615.GP1398@rck.sh \
    --to=roland.kammerer@linbit.com \
    --cc=drbd-announce@lists.linbit.com \
    --cc=drbd-user@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.