Bug 1404420

Summary:	messenger gets stuck in 100% cpu loop after 15 minutes inactivity
Product:	Red Hat Ceph Storage	Reporter:	Samuel Just <sjust>
Component:	RADOS	Assignee:	Samuel Just <sjust>
Status:	CLOSED DUPLICATE	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	ceph-eng-bugs, dzafman, kchai, kdreyer
Target Milestone:	rc
Target Release:	2.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-03 15:46:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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 ***