Bug 1404420 - messenger gets stuck in 100% cpu loop after 15 minutes inactivity
Summary: messenger gets stuck in 100% cpu loop after 15 minutes inactivity
Keywords:
Status: CLOSED DUPLICATE of bug 1402076
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RADOS
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 2.2
Assignee: Samuel Just
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 19:52 UTC by Samuel Just
Modified: 2022-02-21 18:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-03 15:46:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 14120 0 None None None 2016-12-13 19:52:12 UTC

Description Samuel Just 2016-12-13 19:52:12 UTC 
Description of problem:

10.2.4 introduced a bug in the messenger which could cause a messenger thread to use 100% cpu after 15 minutes of inactivity.  It was fixed in 10.2.5

Version-Release number of selected component (if applicable):


How reproducible:

Very

Steps to Reproduce:
1.  Start cluster
2.  Wait 15 minutes
3.  Watch cpu usage spike

Actual results:

3.

Expected results:

not 3.

Additional info:
Comment 2 Ken Dreyer (Red Hat) 2016-12-13 21:50:12 UTC 
I think we can close this as a dup of the general "upgrade to v10.2.5" bug 1402076 ?
Comment 3 Samuel Just 2017-01-03 15:46:27 UTC 

*** This bug has been marked as a duplicate of bug 1402076 ***
Note You need to log in before you can comment on or make changes to this bug.