Bug 1599005

Summary:	[RFE] Filestore split log should show PG that is splitting
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	tbrekke
Component:	RADOS	Assignee:	Josh Durgin <jdurgin>
Status:	CLOSED ERRATA	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	low	Docs Contact:	Bara Ancincova <bancinco>
Priority:	low
Version:	2.5	CC:	ceph-eng-bugs, dzafman, jdurgin, kchai, kdreyer, nojha, rperiyas, vumrao
Target Milestone:	z1	Keywords:	FutureFeature
Target Release:	3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.5-59.el7cp Ubuntu: ceph_12.2.5-45redhat1	Doc Type:	Enhancement
Doc Text:	.Logs now list PGs that are splitting The FileStore split log now shows splitting placement groups (PGs).	Story Points:	---
Clone Of:
Clones:	1613035 (view as bug list)		Environment:
Last Closed:	2018-11-09 00:59:17 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1584264

Description tbrekke 2018-07-07 20:03:27 UTC

Description of problem:

When trying to figure out which pool/pgs are splitting the logging is not helpful.
 
2018-07-07 19:42:32.651577 7fe893a8c700  1 _created [8,0,C] has 9889 objects, starting split.
2018-07-07 19:43:47.153719 7fe893a8c700  1 _created [8,0,C] split completed.

It would be much more helpful if we could get the pg.id in there as well.

Comment 3 Vikhyat Umrao 2018-07-12 01:45:31 UTC

Sent an upstream patch - https://github.com/ceph/ceph/pull/22998

Comment 4 Vikhyat Umrao 2018-08-06 19:43:27 UTC

Luminous backport - https://github.com/ceph/ceph/pull/23454

Comment 7 Vikhyat Umrao 2018-08-13 16:06:48 UTC

(In reply to Vikhyat Umrao from comment #4)
> Luminous backport - https://github.com/ceph/ceph/pull/23454

This one is merged upstream. Moving it to 3.1.z1.

Comment 16 errata-xmlrpc 2018-11-09 00:59:17 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3530