[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: disabling mercurial repositories


  • To: Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Wed, 22 Jun 2022 10:41:32 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=WGTYiYmYf7ItaYZrWZ98gkYlE3bj2CRd0KuSig9IKF4=; b=Rlwn3sjTTeH4KiPUCMw4CypVdEZe29iGjmwiIk0E0Ajuy74lhmkHcnn7qWQvomra8fCzhZXId/uPpUQPRcKsjarQv1xIxgaJXwSkw7+a41PloMcen/AizppLvJR3/VjAv99ybdhHOKRQf5iIj8axu25Cdpi83dFnsqv4tts90mUiBGRltLlyYhS6geEM7Ek9sFXrLd7QUtdYQrVhn9LroveRCKLNspvuZitpNHOYjBQACAVZ36NacQOmbk7Wu+02K0oXq7jIU9vHgw4SyzCbKSOXgAh+IVsdTMHm89c08HbwLghBapD6drX5+E/yOBpDvpNP9zHr4/FwR36cILEkKA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=M1v1a6o+8crOkW3alnHwdaCgQIrWphjEELEGSt/N06BR85pE3ubIxQMPK6aSOHoqJl2EpiFudoULBTvDMR4QYi1sncNLBT2uJF64pTIdOLw7o3G0MKHvO/6SHmDrLGOpFQdj4BCpeQDFv4rucCSL+WvgWjRkpqUZJDBLJYKGwjV79Bp1lzCeb711iErJ3tYcjkHN48o2nHybqsrQwxjwRf64pvOnx2ch53H54fwOLUwj05i+V1CwiGHeKEc37NrUe4mKDEjpz8DFKm5CTgTq4NSY5LqZj9baTWU5wXQxbPMKZnEt6PbMOFFRj75hAlSpcE0lvWk5gWRD7W8VYTP1PQ==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: committers@xxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 22 Jun 2022 08:41:42 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 21.06.2022 15:48, Roger Pau Monné wrote:
> Last week we had a bit of an emergency when a web crawler started
> indexing all our mercurial repositories on xenbits, as caused the load
> on xenbits to go beyond what it can handle.
> 
> As a temporary solution we decided to remove access to mercurial
> repositories, but the contents there are AFAIK only for historical
> repositories, so we might consider completely removing access to
> mercurial repositories.  This would however require migrating any
> repository we care about to git.
> 
> I would like an opinion from committers as well as the broad community
> whether shutting down mercurial repositories and migrating whatever we
> care about is appropriate.  Otherwise we will need to implement some
> throttling to mercurial accesses in order to avoid overloading
> xenbits.

While I wouldn't strictly mind its shutting off or the disabling of
hgweb as was suggested in a reply, either would mean to me personally
that it wouldn't be easy enough anymore to warrant trying to hunt
down the origin of certain Linux side aspects in the 2.6.18-xen tree.
Admittedly me doing so has become increasingly rare over time ...

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.