Hi Everyone,
I ran the command with the JAVA_OPTS and "-b" options mentioned, and even
then, it was taking more than two hours. Then, I canceled the process. I
executed again without the "-b" option and it took about 1 hour.
So, I will enable the cron to run without the "-b" option.
Before the pr
Hi together,
maybe this helps. We run the command like this (after changes to the
discovery config)
sudo -u tomcat7 JAVA_OPTS="-Xmx1024M -Xms1024M -Dfile.encoding=UTF-8"
/dspace/bin/dspace index-discovery -b
so we change the memory limit for java to a gigabyte and it takes 80
minutes for ab
Hi Anisio,
What is too long?
You should only run that command once, or rarely, as part of an upgrade or
maintenance. With the "-b" flag, it creates a full reindex of your
discovery index. On a daily basis (cron), you should run that with no
argument, and it runs over a smaller set of objects.
If
Hello,
The "dspace index-discovery -b" command is taking too long to complete.
Someone has any idea how to solve this problem.
Thanks for help!
--
Carlos ANISIO Monteiro <
monte...@ipen.br>
IPEN/CNEN-SP - Av. Lineu Prestes, 2242 - Cidade Universitária, São Paulo,
Brasil
CEP 05508-000 Tel.(55)
4 matches
Mail list logo
