On Fri, Apr 24, 2009 at 4:46 PM, MakMak wrote:
>
> - We had a 2.3.2 index earlier. We have reindexed using 2.4.1 now.
So the hang still happens with 2.4.1?
> - SAN is ruled out. This occurs even with local file system.
OK.
Have you confirmed things are really hung, vs just taking a long time?
; local filesystem to see if these issues remain. Will keep you posted.
>
> OK keep us posted...
>
>> Anymore hints?
>
> Are you able to reproduce the issue locally? If so we can start
> sprinkling prints...?
>
> Mike
>
> -----
On Tue, Apr 21, 2009 at 6:25 PM, MakMak wrote:
> Ran CheckIndex. This is what it prints out:
>
> cantOpenSegments: false
> numBadSegments: 0
> numSegments: 14
> segmentFormat: FORMAT_HAS_PROX [Lucene 2.4]
> segmentsFileName: segments_2od
> totLoseDocCount: 0
> clean: true
> toolOutOfDate: false
So the SAN is the only
> known difference?
>
> Mike
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
On Mon, Apr 20, 2009 at 6:07 PM, MakMak wrote:
> I made a standalone tool like you suggested which prints out the size of
> each doc in the index, none of the docs are more than 1MB !!! The queries
> are the same. They repeat throughout the test. We give about 6GB of heap to
> the application a
hy. Nothing else changed in the upgrade?
>
> Mike
>
> -----
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>
>
--
View
On Fri, Apr 17, 2009 at 5:05 AM, MakMak wrote:
> I am not retrieving many docs, the problem is that the whole file is stored
> in the doc. I need the file content for highlighter to work. But the files
> are normal-sized text files which in any case should not exceed 10-15mb.
> Retrieving 25 of t
;
> Mike
>
>
>
--
View this message in context:
http://www.nabble.com/readModifiedUTF8String-stuck-tp23089805p23093956.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe
egmentReader.document(MultiSegmentReader.java:259)
> at org.apache.lucene.index.IndexReader.document(IndexReader.java:637)
> at org.apache.lucene.search.IndexSearcher.doc(IndexSearcher.java:91)
> ----
didnt rebuild the index. Also, the indices reside
on a SAN. Is the above possible due to some n/w issue that might have
happened between the SAN and the appserver?
--
View this message in context:
http://www.nabble.com/readModifiedUTF8String-stuck-tp23089805p23092183.html
Sent from the Lucene - Java
What I dont understand is, how can the thread be stuck at at
java.lang.String.(String.java:208) ???
-thanks a lot
--
View this message in context:
http://www.nabble.com/readModifiedUTF8String-stuck-tp23089805p23089805.h
11 matches
Mail list logo
