[ 
https://issues.apache.org/jira/browse/LUCENE-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216025#comment-16216025
 ] 

Mykhailo Demianenko commented on LUCENE-7999:
---------------------------------------------

Thank you! [~mikemccand] Unfortunately I do not have precise information on how 
old this particular index was (most probably a couple of years). But yes we 
refresh indexes quite a lot since we need to ensure that readers always see the 
latest available snapshot of the data.

> Invalid segment file name
> -------------------------
>
>                 Key: LUCENE-7999
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7999
>             Project: Lucene - Core
>          Issue Type: Bug
>    Affects Versions: 5.x, 6.x, 7.0
>            Reporter: Mykhailo Demianenko
>            Priority: Minor
>         Attachments: LUCENE-7999.patch, segmentName.patch
>
>
> After really long and intensive index usage its possible to overflow counter 
> that used to generate new segment name that will not satisfy validation 
> criteria:
> Caused by: java.lang.IllegalArgumentException: invalid codec filename 
> '_-zik0zk_Lucene54_0.dvm', must match: _[a-z0-9]+(_.*)?\..*
>     at 
> org.apache.lucene.index.SegmentInfo.checkFileNames(SegmentInfo.java:280)
>     at org.apache.lucene.index.SegmentInfo.addFiles(SegmentInfo.java:262)
>     at org.apache.lucene.index.SegmentInfo.setFiles(SegmentInfo.java:256)
>     at org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:4080)
>     at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3655)
>     at 
> org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:588)
>     at 
> org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:626)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to