Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] [jgit-dev] Fwd: [eclipse.org-committers] Service outage
On Fri, Apr 25, 2025 at 11:04 AM Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
On Thu, Apr 24, 2025 at 6:49 PM Luca Milanesio via jgit-dev <jgit-dev@xxxxxxxxxxx> wrote:
FYI, the Eclipse Foundation has a Service Outage on the ECA validation, which is used for validating incoming changes to eclipse.gerrithub.io.

Please note that you won’t be able to upload or amend existing changes on eclipse.gerrithub.io until the outage is resolved.
Existing changes can go over reviews and comments, as they won’t involve the ECA validation plugin.

Since last night pushing to the jgit repo works again after they restored the tier 1 services including ECA API.

See status at https://www.eclipsestatus.io/incident/549796:

Cluster storage is slowly being restored. All Tier I services have been restored with minor degradations.
Other services are being restored using temporary storage services.

Eclipse IT reported that recovery of the storage cluster doesn't progress as expected and offered to restore CI instances
from last backup which I now requested for JGit and EGit CI instances in https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5966

-Matthias
 
 
Luca.

Begin forwarded message:

From: "Denis Roy via eclipse.org-committers" <eclipse.org-committers@xxxxxxxxxxx>
Subject: [eclipse.org-committers] Service outage
Date: 24 April 2025 at 15:34:06 BST
To: Eclipse Committers <eclipse.org-committers@xxxxxxxxxxx>
Reply-To: Eclipse Committers general discussion <eclipse.org-committers@xxxxxxxxxxx>

Folks,

You're likely aware of a massive outage currently taking place. It is affecting many services, notably user authentication, CI (Jenkins) and the ECA validation.

While investigating a performance issue with our high-availability storage cluster, that same technology which was intended to not fail has, disappointingly, failed. The team is working feverishly to restore the cluster, and in the interim, is reverting to legacy storage to restore some services more rapidly.

Unfortunately, the demands on storage from CI are quite large, both in terms of capacity as well as operations/second, and cannot be restored to legacy storage.

We're so very sorry that this has happened.  We understand how incredibly disruptive this is to your ability to do work. As usual, once service is restored, we'll analyse and assess what happened so that we can revise our strategy, and share the details with you.

In the meanwhile, I encourage you to follow updates at https://www.eclipsestatus.io/ (below the fold are the maintenance and outage events).


Denis


--
Denis Roy
Director, IT Services | Eclipse Foundation
Eclipse Foundation: The Community for Open Innovation and Collaboration
_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-committers

_______________________________________________
jgit-dev mailing list
jgit-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jgit-dev

Back to the top