Bug 628611

Summary:	jobserver: maintenance of history files and their indices needs clarity
Product:	Red Hat Enterprise MRG	Reporter:	Pete MacKinnon <pmackinn>
Component:	condor	Assignee:	Pete MacKinnon <pmackinn>
Status:	CLOSED NOTABUG	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.3	CC:	iboverma, jneedle, ltoscano, matt
Target Milestone:	2.0
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-21 18:34:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pete MacKinnon 2010-08-30 14:25:18 UTC

Currently, the Job Server daemon on startup will index all the history files it finds in its configured location (HISTORY dir). It will also regularly garbage collect any orphaned indices that no longer have a matching history file (by inode name).

However, Matt has stated that by design Grid admins could choose to throw away the larger history files in favour of keeping just the smaller index files.

Need some clearer design requirements here.

Comment 1 Matthew Farrellee 2010-08-30 18:41:26 UTC

Kicking this as an RFE for a future release.

The current code is reported to work and garbage collect the indices. Before removing the garbage collecting functionality from the JS, another defined mechanism should be provided.