Rescheduled Datatracker Outage to 11Apr2023 (was Datatracker outage 19Jan2023 to shift database engines)

Robert Sparks <rjsparks@nostrum.com> Tue, 10 January 2023 23:23 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0959CC14F693 for <ietf-announce@ietfa.amsl.com>; Tue, 10 Jan 2023 15:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.076
X-Spam-Level:
X-Spam-Status: No, score=-2.076 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s2bpbobyra4Z for <ietf-announce@ietfa.amsl.com>; Tue, 10 Jan 2023 15:23:03 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC4C8C14F5E0 for <ietf-announce@ietf.org>; Tue, 10 Jan 2023 15:23:02 -0800 (PST)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 30ANN09T030118 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <ietf-announce@ietf.org>; Tue, 10 Jan 2023 17:23:01 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1673392981; bh=pdott+mrVjcoSZySPqYUmEkBBCmo9opJZs92J/hTj7g=; h=Date:From:To:Reply-To:References:Subject:In-Reply-To; b=a2BgalHQEhdAPhk5cHe4xAygCW31849bh0owZarEzOgvof8yH1lWPYe4jfsA2sTUW QhPelfMQSbusTy7fVuc3alH53/VIBfg/GVTy5/AdvK6PKey+FyT7ZzLDwzOXvRsgJX dpdWoaovJAnygIl24uUwE7b50JSuexMa+IyxA4ak=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <d4fb942c-3e39-6775-d931-9b8837187d2d@nostrum.com>
Date: Tue, 10 Jan 2023 17:22:55 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
Content-Language: en-US
From: Robert Sparks <rjsparks@nostrum.com>
To: ietf-announce@ietf.org
Reply-To: tools-discuss <tools-discuss@ietf.org>
References: <b5a1f390-04ac-5f4f-c242-f7238d3b600e@nostrum.com>
Subject: Rescheduled Datatracker Outage to 11Apr2023 (was Datatracker outage 19Jan2023 to shift database engines)
In-Reply-To: <b5a1f390-04ac-5f4f-c242-f7238d3b600e@nostrum.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/UKz7nKHWxlPFlHWlkAJrWUrhfy0>
X-Mailman-Approved-At: Tue, 10 Jan 2023 15:28:40 -0800
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jan 2023 23:23:07 -0000

We have discovered issues that prevent shifting the datatracker to 
postgresql on 19Jan.

These will take long enough to remedy that we will be in the active 
pre-IETF 116 period by the time we are ready, so we are rescheduling the 
shift until after that meeting.

This outage is now scheduled for Tuesday 11Apr2023 just after 21:00 UTC.

The essence of the issue is in the different collation between MySQL and 
Postgresql. Our initial tests indicated that we were safe proceeding to 
Postgresql's case-sensitive collation with the code changes we've 
already made, but more detailed work in December and early January have 
shown that more are necessary.

Robert Sparks

Tools Project Manager


On 12/19/22 3:23 PM, Robert Sparks wrote:
> We plan to take the datatracker offline Thursday 19Jan2023 just after 
> 21:00 UTC to shift the underlying database to postgresql.
>
> This change will bring some immediate performance improvements, and 
> more as we continue to tune after the transition.
>
> We currently expect at most 30 minutes (probably much less) of 
> downtime. I'll refine the time estimate as the date grows closer.
>
> Cloudflare will continue to serve cached pages for users who are not 
> logged in during that time.
>
> Please direct any questions directly to me or to tools-discuss@ietf.org
>
> Robert Sparks
>
> Tools Project Manager
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce