Project

Profile

Help

Task #1014

closed

Short Term Improvements for Pulp's use of MongoDB

Added by dkliban@redhat.com over 8 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
(Total: 0:00 h)
Platform Release:
2.7.1
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

This is a tracker bug to make sure that we get all the issues related to MongoDB and replica sets resolved in a timely manner.


Subtasks 8 (0 open8 closed)

Issue #974: GET of a task sometimes 404s on first requestCLOSED - CURRENTRELEASEdkliban@redhat.comActions
Issue #1012: If the first database seed listed in server.conf is not the current Primary replica, Pulp will not be able to write to the databaseCLOSED - CURRENTRELEASEdkliban@redhat.comActions
Issue #956: Pulp's Celery result backend connection cannot use Mongo replica sets with automatic failoverCLOSED - CURRENTRELEASEdkliban@redhat.comActions
Story #1: As a user, I can have Pulp attempt use auto_retry application wide using the 'unsafe_autoretry' parameterCLOSED - CURRENTRELEASEamacdona@redhat.com

Actions
Story #934: Update mongoengine dependency to 0.9CLOSED - CURRENTRELEASEbmbouter

Actions
Refactor #1084: Stop Pulp from using the Celery results backendCLOSED - CURRENTRELEASEdkliban@redhat.com

Actions
Issue #1065: DeprecationWarning on pulp-manage-dbCLOSED - CURRENTRELEASEamacdona@redhat.comActions
Issue #1139: Fix Pulp's use of replica sets replica setsCLOSED - CURRENTRELEASEActions

Also available in: Atom PDF