Actually, in examining the host system more closely, there is a
failed drive... therefore, write-back cache is disabled.
I believe we have a spare here -- I'll see if I can replace it
today.
Denis
On 09/14/2012 09:59 AM, Denis Roy
wrote:
Alex,
Block device performance is never spectacular on these virtualized
machines -- that's why we use them for redundant front-ends.
However, having a single CPU and 1G of RAM is certainly not
helping. If I add a CPU and increase RAM to 3G can I restart the
VM? Will Nexus start itself automatically?
Thanks,
Denis
On 09/06/2012 05:33 PM, Alex Blewitt wrote:
I've updated the Maven configuration so
that it shouldn't have the same duplication of data for
repo1/repo2 as there's now a 'central' which has repo1/repo2 as
mirrors.
I've also discovered that basically the jobs on nexus are
broken, and there's nothing obvious as to why. I suspect a nexus
restart may fix it, but since I don't know if it's being used or
not, I suggest doing it at a quieter time of day.
The trash appears to build up and never get emptied; the
automated empty job appears to fail as well. Plus, the
performance of IO on the VM is so hideously bad that deleting
files is a real nightmare; to clean up the code, I had to
execute:
cd sonatype-work/nexus/trash
for i in */*/*
do
rm -rf $i &
done
Whilst you can theoretically do this in a single rm -rf, the
jobs appear to be the only way to do this in a reasonable period
of time. As a result we now have almost 1/2 the box space free.
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 19G 8.3G 9.7G 47% /
To avoid the problems in the future, if Nexus isn't going to
play ball, we should consider setting up a cron job to do the
same thing, or log in and periodically flush it manually.
Perhaps this will be fixed with a Nexus 2.x install instead.
Alex
_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev
|