2014-10-06

Remove old messages...

Originally Posted By: mburukenya
Hi,
I think my queue server is unable to delete orphaned dirs. Is there any way I can delete them manually.

LOG FILE
Initialize logger..
[Mon, 06 Oct 2014 01:20:28 -0700] Remove old messages..
[Mon, 06 Oct 2014 01:20:28 -0700] In queue loop!! IndexerAndScheduler
[Mon, 06 Oct 2014 01:20:28 -0700] ..Indexer still deleting 1 of 3 orphaned dirs Current memory usage:4713296
[Mon, 06 Oct 2014 01:20:28 -0700] IndexerAndScheduler peak memory usage so far: 4762704!!
[Mon, 06 Oct 2014 01:20:28 -0700] IndexerAndScheduler is waiting for start message

[Mon, 06 Oct 2014 01:20:33 -0700] IndexerAndScheduler peak memory usage so far: 4762704!!
[Mon, 06 Oct 2014 01:20:33 -0700] IndexerAndScheduler is waiting for start message

[Mon, 06 Oct 2014 01:20:38 -0700] IndexerAndScheduler peak memory usage so far: 4762704!!
[Mon, 06 Oct 2014 01:20:38 -0700] IndexerAndScheduler is waiting for start message
'''Originally Posted By: mburukenya''' Hi,<br>I think my queue server is unable to delete orphaned dirs. Is there any way I can delete them manually.<br><br>LOG FILE<br>Initialize logger..<br>[Mon, 06 Oct 2014 01:20:28 -0700] Remove old messages..<br>[Mon, 06 Oct 2014 01:20:28 -0700] In queue loop!! IndexerAndScheduler<br>[Mon, 06 Oct 2014 01:20:28 -0700] ..Indexer still deleting 1 of 3 orphaned dirs Current memory usage:4713296<br>[Mon, 06 Oct 2014 01:20:28 -0700] IndexerAndScheduler peak memory usage so far: 4762704!!<br>[Mon, 06 Oct 2014 01:20:28 -0700] IndexerAndScheduler is waiting for start message<br><br>[Mon, 06 Oct 2014 01:20:33 -0700] IndexerAndScheduler peak memory usage so far: 4762704!!<br>[Mon, 06 Oct 2014 01:20:33 -0700] IndexerAndScheduler is waiting for start message<br><br>[Mon, 06 Oct 2014 01:20:38 -0700] IndexerAndScheduler peak memory usage so far: 4762704!!<br>[Mon, 06 Oct 2014 01:20:38 -0700] IndexerAndScheduler is waiting for start message

-- Remove old messages..
That log message is actually not accurate. It should say that it is checking directory 1 of 3
to see whether any are orphaned. At the point that it writes the message, it hasn't determined
in that directory whether or not there are any orphaned bundles. So you can safely ignore that
message. I will modify what it says in the next release. Two places you could manually
look for not in use directories are:
WORK_DIRECTORY/cache
and
WORK_DIRECTORY/schedules
Folders with timestamps in their names that don't correspond to any crawl you want to keep
can be safely deleted.
That log message is actually not accurate. It should say that it is checking directory 1 of 3<br>to see whether any are orphaned. At the point that it writes the message, it hasn't determined<br>in that directory whether or not there are any orphaned bundles. So you can safely ignore that<br>message. I will modify what it says in the next release. Two places you could manually<br>look for not in use directories are:<br>WORK_DIRECTORY/cache<br>and<br>WORK_DIRECTORY/schedules<br>Folders with timestamps in their names that don't correspond to any crawl you want to keep<br>can be safely deleted.
X