Chris, AFAIK, the cleanup operation is run at the end of the default workflow. Therefore I would take a look at your current workflow definition to make sure that the operation is still there. If it is, then I am as puzzled as you :P
Best regards Rubén P.S: Sorry for the duplicate response. Wrong address... 2011/9/18 Christopher Brooks <[email protected]> > Hi tobias, > > Couple of quick questions; > > If we are using red5 streaming can we drop downloads? We intend only to > support streaming atm, so having the download distribution in our workflow > seems like a misconfiguration. Or is download neccessary for streaming to > engage? (E.g. Segment previews?) > > Second, our engage server has its own storage space, it's not shared with > the workers/etc. In this configuration, any thoughts on why the workspace > isn't being cleaned up? (And on top of this, should we add engage to the > shared storage so it doesn't need to make its own workspace copy?) > > Best regards, > > Chris > -----Original Message----- > From: Tobias Wunden <[email protected]> > Sender: [email protected] > Date: Sat, 17 Sep 2011 08:39:18 > To: Matterhorn Users<[email protected]> > Reply-to: Matterhorn Users <[email protected]> > Subject: Re: [Matterhorn-users] Engage storing multiple copies of files > > Hi Chris, > > there is no ticket open as this is intended behavior (or a bug by desing > :-) The reasoning behind having three separate copies is the following: > > 1) /workspace is a temporary file and should be removed when running the > "cleanup" operation > > 2) The items in /downloads and /stream cannot be linked against one another > because both are individual distribution channels and have (by design) no > knowledge about each other. In addition > > 3) In production environments, you won't usually serve downloads and/or > streams from the box that is running your ui, because ui performance may > seriously be affected by a peak in downloads or streaming. Instead, there is > most often separate downlaod and streaming servers, and the two copies go to > two different mounts, hence another reason not to use hard links. But as > mentionend under 2), it is not possible anyway. > > On solution would be to write your own distribution handler wich puts a > copy somewhere an then creates links to your set of distribution folders. > > Tobias > > On 17.09.2011, at 02:51, [email protected] wrote: > > > Hi, > > > > I know this has come up before, but I couldn't find discussion of the > issue or a > > ticket so I'm hoping someone can point me to the right place. Our engage > > instance is keeping three copies of each file, one in /downloads, one in > > /streams, and one in /workspace. > > > > Can some of these directories be nuked without effecting functionality? > > > > Is a ticket open for the issue? > > > > We've got a fairly moderate system going right now (30 gig of lectures in > engage > > if you count them once), but it's only the second week of a 14 week > semester, so > > that's going to jump to around 210 gig by the end of term, which brings > us to > > just over half a terabyte. > > > > I wasn't planning on eating up this much space for that server for the > whole > > year... > > > > Chris > > _______________________________________________ > > Matterhorn-users mailing list > > [email protected] > > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
