all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Dietmar Maurer <dietmar@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] ui: tape/BackupOverview: increase timeout for media-set content
Date: Tue, 13 Jul 2021 09:45:07 +0200	[thread overview]
Message-ID: <43e42748-edba-5a1d-a3a8-25fcbd723a6e@proxmox.com> (raw)
In-Reply-To: <20210713070914.479223-1-d.csapak@proxmox.com>

applied

On 7/13/21 9:09 AM, Dominik Csapak wrote:
> a single catalog can be over 100MiB, and a media-set can have multiple
> catalogs to read (no technical upper limit). On slow disks, this can
> take much longer than 30 seconds (the default timeout).
>
> The real solution would be to have some kind of index only for the gui
> relevant part, e.g. a table in the beginning of the catalog, or
> alternatively a seperate file with that info. Until we have such a
> solution increase the timeout as a stopgap.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
>   www/tape/BackupOverview.js | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/www/tape/BackupOverview.js b/www/tape/BackupOverview.js
> index 4ba53157..c368640c 100644
> --- a/www/tape/BackupOverview.js
> +++ b/www/tape/BackupOverview.js
> @@ -125,6 +125,9 @@ Ext.define('PBS.TapeManagement.BackupOverview', {
>   		let list = await Proxmox.Async.api2({
>   		    method: 'GET',
>   		    url: `/api2/extjs/tape/media/content`,
> +		    // a big media-set with large catalogs can take a while to load
> +		    // so we give a big (5min) timeout
> +		    timeout: 5*60*1000,
>   		    params: {
>   			'media-set': media_set_uuid,
>   		    },




      reply	other threads:[~2021-07-13  7:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13  7:09 [pbs-devel] " Dominik Csapak
2021-07-13  7:45 ` Dietmar Maurer [this message]

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=43e42748-edba-5a1d-a3a8-25fcbd723a6e@proxmox.com \
    --to=dietmar@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pbs-devel@lists.proxmox.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal