Project

Profile

Help

Issue #1564

closed

Unacked messages in resource_manager queue

Added by bmbouter about 7 years ago. Updated almost 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.7.0
Platform Release:
2.8.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

After executing a "heavy" workload, the resource_manager queue may have unacked messages in it. To reproduce you can:

1. Execute the heavy workload and let it finish. For instance you could sync many repos and publish them.

2. List the Qpid queue statistics with:

qpid-stat -q

3. Observe a output like the following:

queue                                                                             dur  autoDel  excl  msg   msgIn  msgOut  bytes  bytesIn  bytesOut  cons  bind 
=================================================================================================================================================================
<snip>
resource_manager                                                                  Y                     19   338    319    33.4k   567k     534k        1     2
<snip>

4. Observe that all Pulp tasks have completed with state finished, and yet there are still messages in the 'msg' column. 19 in the example above. You can verify all Pulp tasks as being completed by connecting to mongo, switching to the pulp_database, and running the following command. If all pulp tasks are finished that query will return 0.

db.task_status.find({ state:{ $ne: "finished" } } ).count()

Note: This has been observed on both EL6 and EL7, and it may be observable on Fedoras also.

Any of the unacked messages will be "rerun" when the resource_manager restarts because the message broker will redeliver them. This is a user noticeable defect.

Also available in: Atom PDF