Project

General

Profile

Bug #25214

valgrind failures related to --max-threads prevent radosgw from starting

Added by Casey Bodley 4 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
High
Assignee:
-
Target version:
-
Start date:
08/01/2018
Due date:
% Done:

0%

Source:
Tags:
Backport:
mimic luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

The rgw/verify suite is failing after changing the default thread pool size to 512.

http://pulpito.ceph.com/teuthology-2018-07-30_03:05:02-rgw-master-distro-basic-smithi/

2018-08-01T11:23:48.360 INFO:tasks.rgw.c1.client.1:Started
2018-08-01T11:23:48.360 INFO:tasks.rgw:Polling c2.client.1 until it starts accepting connections on http://smithi045.front.sepia.ceph.com:7282/
2018-08-01T11:23:48.362 WARNING:requests.packages.urllib3.connectionpool:Retrying (Retry(total=9, connect=7, read=None, redirect=None)) after connection broken by 'NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f0d385cd850>: Failed to establish a new connection: [Errno 111] Connection refused',)': /
2018-08-01T11:23:50.366 WARNING:requests.packages.urllib3.connectionpool:Retrying (Retry(total=8, connect=6, read=None, redirect=None)) after connection broken by 'NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f0d385cda10>: Failed to establish a new connection: [Errno 111] Connection refused',)': /
2018-08-01T11:23:54.368 WARNING:requests.packages.urllib3.connectionpool:Retrying (Retry(total=7, connect=5, read=None, redirect=None)) after connection broken by 'NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f0d385cdc90>: Failed to establish a new connection: [Errno 111] Connection refused',)': /
2018-08-01T11:23:55.413 INFO:tasks.rgw.c1.client.1.smithi069.stderr:Use --max-threads=INT to specify a larger number of threads
2018-08-01T11:23:55.413 INFO:tasks.rgw.c1.client.1.smithi069.stderr:and rerun valgrind
2018-08-01T11:23:55.413 INFO:tasks.rgw.c1.client.1.smithi069.stderr:
2018-08-01T11:23:55.413 INFO:tasks.rgw.c1.client.1.smithi069.stderr:valgrind: the 'impossible' happened:
2018-08-01T11:23:55.413 INFO:tasks.rgw.c1.client.1.smithi069.stderr:   Max number of threads is too low


Related issues

Related to rgw - Bug #24544: change default rgw_thread_pool_size to 512 Resolved 06/15/2018
Copied to rgw - Backport #25217: luminous: valgrind failures related to --max-threads prevent radosgw from starting Resolved
Copied to rgw - Backport #25218: mimic: valgrind failures related to --max-threads prevent radosgw from starting Resolved

History

#1 Updated by Casey Bodley 4 months ago

  • Related to Bug #24544: change default rgw_thread_pool_size to 512 added

#2 Updated by Matt Benjamin 4 months ago

can we change the valgrind invocation as suggested in the output?

#3 Updated by Casey Bodley 4 months ago

  • Status changed from New to Need Review
  • Backport set to mimic luminous

#4 Updated by Casey Bodley 4 months ago

  • Status changed from Need Review to Pending Backport

#5 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #25217: luminous: valgrind failures related to --max-threads prevent radosgw from starting added

#6 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #25218: mimic: valgrind failures related to --max-threads prevent radosgw from starting added

#7 Updated by Nathan Cutler 3 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF