[
https://issues.apache.org/jira/browse/LUCENE-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679767#comment-14679767
]
Dawid Weiss edited comment on LUCENE-6725 at 8/10/15 8:15 AM:
--
Depends on the hardware (number of CPUs, disk drives, memory) and on randomized
seed selection (because iteration loops, codecs, etc. vary). On my modest
desktop the results are (trunk):
{code}
cd lucene
time ant test-core
Total time: 3 minutes 6 seconds
real3m7.098s
user21m5.092s
sys 0m24.440s
time ant test
Total time: 7 minutes 5 seconds
real7m5.494s
user57m0.224s
sys 1m36.848s
{code}
So not *that* long. Repeating a few times makes sense though (again:
randomization). If you wish to run longer tests, you need to enable nightly/
slow too:
{code}
ant test -Dtests.nightly=true -Dtests.slow=true
{code}
If you wish to experiment with 3.5, then you could try to narrow down the
offending/ crashing test by running a single suite, for example:
{code}
ant test-core -Dtestcase=TestDocumentWriter
{code}
Note the test runner (and command line options) have changed quite a lot since
3.5.
was (Author: dweiss):
Depends on the hardware (number of CPUs, disk drives, memory) and on randomized
seed selection (because iteration loops, codecs, etc. vary). On my modest
desktop the results are (trunk):
{code}
cd lucene
time ant test-core
Total time: 3 minutes 6 seconds
real3m7.098s
user21m5.092s
sys 0m24.440s
time ant test
{code}
So not *that* long. Repeating a few times makes sense though (again:
randomization). If you wish to run longer tests, you need to enable nightly/
slow too:
{code}
ant test -Dtests.nightly=true -Dtests.slow=true
{code}
If you wish to experiment with 3.5, then you could try to narrow down the
offending/ crashing test by running a single suite, for example:
{code}
ant test-core -Dtestcase=TestDocumentWriter
{code}
Note the test runner (and command line options) have changed quite a lot since
3.5.
Reindex crashes the JVM
---
Key: LUCENE-6725
URL: https://issues.apache.org/jira/browse/LUCENE-6725
Project: Lucene - Core
Issue Type: Bug
Components: core/index
Affects Versions: 3.5
Environment: Solaris 10 1/13 (Update 11) Patchset applied.
Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC
CPU:total 64 v9, popc, vis1, vis2, vis3, blk_init, cbcond, sun4v, niagara_plus
Memory: 8k page, physical 25165824k(3240848k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (24.75-b04) for solaris-sparc JRE
(1.7.0_75-b13)
Reporter: Jan Eerdekens
Priority: Minor
Attachments: hs_err_pid18938.log, lucene-3.5-ant-test-results.txt
We're using Liferay which uses Lucene behind the screens to index things like
documents, web content, users, etc... . When we trigger a full reindex via
the Liferay Control Panel, which uses IndexWriter.deleteAll(), the JVM
crashes and generates a dump with the following message:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x78de94a8, pid=18938, tid=2478
#
# JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build
1.7.0_75-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode
solaris-sparc compressed oops)
# Problematic frame:
# J 5227 C2
org.apache.lucene.index.IndexFileNames.segmentFileName(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
(44 bytes) @ 0x78de94a8 [0x78de9480+0x28]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org