Gitlab had performance issues after database split-brain

From: Wei Shan <weishan(dot)ang(at)gmail(dot)com>
To: pgsql-advocacy(at)postgresql(dot)org
Subject: Gitlab had performance issues after database split-brain
Date: 2018-04-27 10:05:22
Message-ID: CAFe9ZTpzzJNw=Vx_W7o8sGb2_enD1-E+hb6MbdXLOuq-7KngnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

Gitlab had some issues recently with PostgreSQL.

- http://www.theregister.co.uk/2018/04/27/gitlab_outage_april_2018/
-
https://docs.google.com/document/d/1_IzyO-jwqb7UFl0A28D1gR4EaU99cEnoUSD9o8q4eZw/edit#

From their timeline report, it looks like they were using repmgr. Somehow,
I don't understand how they manage to get split-brain from a primary
failure with a 5 node cluster.

Does anyone have more insights to this?

--
Regards,
Ang Wei Shan

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Simon Riggs 2018-04-27 11:28:18 Re: Gitlab had performance issues after database split-brain
Previous Message Jan Karremans 2018-04-23 19:42:23 Talking about PostgreSQL