Project

General

Profile

Actions
Copy link

Bug #7549

closed

Mon deadlock

Added by David Zafman about 10 years ago. Updated about 10 years ago.

Status:
Won't Fix
Priority:
High
Assignee:
-
Category:
Monitor
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I was running test/vstart_wrapped_tests.sh built from 60c9aafaf0ff033dca22606ea811c792f1cda781. It looks like multiple threads are doing memory allocation while one thread is doing HeapProfilerDump(). I suspect this was caused when termination of mon after testing was over. It is likely a tcmalloc bug, unless our code is corrupting the memory allocator's data structures.

Files

mon-deadlock.txt (11.6 KB) mon-deadlock.txt All backtraces of ceph-mon David Zafman, 02/26/2014 02:57 PM
Actions
Copy link
 #1

Updated by David Zafman about 10 years ago

  • Category set to Monitor
Actions
Copy link
 #2

Updated by David Zafman about 10 years ago

I did add a -d to the vstart.sh invocation in the test/vstart_wrapper.sh script.

Actions
Copy link
 #3

Updated by Samuel Just about 10 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #4

Updated by David Zafman about 10 years ago

  • Status changed from New to Won't Fix

This is most likely a bug in the older libgoogle-perftools* which is part of the Precise Ubuntu distribution. Either it must be upgraded by building a newer version or switch to a newer version of Ubuntu.

Actions
Copy link

Also available in: Atom PDF