Below is a note from Kris:
"...What I'm thinking is that when the user changes the
setting any new ARC files created after that point will
be written to the new location but any currently open
ARCs will be completed where they are.
"The reason for this is that a crawl here was a bit
misconfigured and is downloading ARCs to a disk with
insufficient space for the amount of data we are
gathering. Even moving the ARCs away the crawler will
exhaust available space overnight..."
This will be awkward to do because the arc dir is set
once on initialization of ARCWriterProcessor. The
arcdir location is passed into the ARCWriterPool which
in turn passes it to ARCWriters as they are created.
One thing to look at is having ARCWriterProcessor
monitor for arcdir changes. It could then update
ARCWriterPool which could then pass on the message to
all members of the ARCWriter pool (If the arcdir
directory were a static it'd make things a little easier).
Michael Stack
i/o
None
Public
|
Date: 2007-03-14 01:30
|
|
Date: 2005-01-13 02:54 Logged In: YES |
|
Date: 2004-05-14 15:19 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2005-01-13 02:54 | stack-sf |
| close_date | - | 2005-01-13 02:54 | stack-sf |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use