Project

General

Profile

Bug #1308

Mongo running out of disk space

Added by Rogers, Chris almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Online reconstruction
Target version:
Start date:
12 July 2013
Due date:
% Done:

100%

Estimated time:
Workflow:
New Issue

Description

Suggest two options:

i. Either we clear the mongo cache for events more than, say, 10 minutes old (preferred)
ii. Or we put the mongodb in the /home/ partition which has few 10s of Gb free

Prefer i. as it probably solves some other problems

#1

Updated by Rogers, Chris almost 11 years ago

Should say this is for onrec01

#2

Updated by Rogers, Chris almost 11 years ago

Implemented mongo docstore as a "capped" docstore with maximum number of documents set by default to 1000; this corresponds to about 1000/3 spills, implies about 10 minutes of running.

#3

Updated by Rogers, Chris almost 11 years ago

Watching http://test.mice.rl.ac.uk/job/MAUS_online/12/ before I merge to trunk... would like to test in control room against cosmics over the weekend

#4

Updated by Rogers, Chris almost 11 years ago

So I installed rogers branch in the control room for testing. Found out that mongodb does not seem to like limiting number of events but instead seems to be happier limiting overall file size, so I will give this a go instead. Will take cosmics over the weekend and see how it goes.

The other place I can trip up (in a similar vein) will be on log file size, where I don't use a proper logging application and so may get into trouble...

#5

Updated by Rogers, Chris almost 11 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Merged in r965

#6

Updated by Rajaram, Durga almost 11 years ago

  • Target version changed from Future MAUS release to MAUS-v0.6.0

Also available in: Atom PDF