Project

General

Profile

Actions

Bug #40018

closed

crash in io_context thread when lots of connections abort

Added by Ali Maredia almost 5 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
High
Target version:
-
% Done:

0%

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

Description

During a small percentage of runs of the full rgw:verify suite the radosgw crashes in the middle of a run of the java s3-tests suite.

See .txt files with snippits of teuthology logs and the link to the logs themselves.


Files

java_s3_tests_crash_log_1.txt (238 KB) java_s3_tests_crash_log_1.txt Ali Maredia, 05/23/2019 09:47 PM
java_s3_tests_crash_log_2.txt (100 KB) java_s3_tests_crash_log_2.txt Ali Maredia, 05/23/2019 09:47 PM

Related issues 4 (1 open3 closed)

Related to rgw - Bug #57784: beast frontend crashes on exception from socket.local_endpoint()Pending BackportCasey Bodley

Actions
Copied to rgw - Backport #41569: nautilus: crash in io_context thread when lots of connections abortResolvedAbhishek LekshmananActions
Copied to rgw - Backport #41570: mimic: crash in io_context thread when lots of connections abortResolvedAbhishek LekshmananActions
Copied to rgw - Backport #41571: luminous: crash in io_context thread when lots of connections abortRejectedActions
Actions #2

Updated by Matt Benjamin almost 5 years ago

  • Status changed from New to Triaged
  • Assignee set to Casey Bodley
Actions #3

Updated by Abhishek Lekshmanan almost 5 years ago

  • Priority changed from Normal to High
Actions #4

Updated by Abhishek Lekshmanan almost 5 years ago

it looks like the io_context::run() ec overload variant is deprecated. https://www.boost.org/doc/libs/1_66_0/doc/html/boost_asio/reference/io_context/run/overload2.html

Following down the stacktrace, it seems like the ec value is ignored in boost::asio::detail::scheduler_operation::complete

Actions #5

Updated by Casey Bodley almost 5 years ago

  • Subject changed from RGW is crashing after some Java S3 tests to crash in io_context thread when lots of connections abort
Actions #6

Updated by Abhishek Lekshmanan over 4 years ago

  • Status changed from Triaged to In Progress
  • Assignee changed from Casey Bodley to Abhishek Lekshmanan
Actions #7

Updated by Nathan Cutler over 4 years ago

  • Status changed from In Progress to Pending Backport
  • Backport set to mimic, nautilus
  • Pull request ID set to 29967
Actions #8

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41569: nautilus: crash in io_context thread when lots of connections abort added
Actions #9

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41570: mimic: crash in io_context thread when lots of connections abort added
Actions #10

Updated by Nathan Cutler over 4 years ago

  • Backport changed from mimic, nautilus to luminous, mimic, nautilus
Actions #11

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41571: luminous: crash in io_context thread when lots of connections abort added
Actions #12

Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions #13

Updated by Casey Bodley over 1 year ago

  • Related to Bug #57784: beast frontend crashes on exception from socket.local_endpoint() added
Actions

Also available in: Atom PDF