Publishing issues 2014-02-12
This summary is created by Generative AI and may differ from the actual content.
Overview
some publishes to the registry were failing. The root cause was an undiscovered bug in CouchDB which caused replication to fail, leading to conflicts when users tried to publish. There was however a 1 in 3 chance that even with both replicas delayed, you could both read from and write to the master, in which case your publish would have worked (which is why it worked for some people when they retried). Also an additional, incomplete replacement replica was accidentally in production rotation.
Impact
some publishes to the registry were failing
Trigger
an undiscovered bug in CouchDB which caused replication to fail
Detection
better monitoring of the replication status of the two downstream servers
Resolution
removed the additional, incomplete replacement replica from production
Root Cause
an undiscovered bug in CouchDB which caused replication to fail, leading to conflicts when users tried to publish