[OAK-9408] OakStreamingIndexFile negative file length

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.38.0
• Fix Version/s: 1.40.0
• Component/s: indexing
• Assignee: Amrit Verma
• Reporter: Amrit Verma
• Created: 16/Apr/21 06:47
• Updated: 03/Jun/21 14:53
• Resolved: 19/Apr/21 08:03

Description

The calculation done here results in negative file length if blob length comes as 0.

Negative file length causes confusion when it gets reported in errors like -

org.apache.jackrabbit.oak.plugins.index.search.BadIndexTracker Could not open the Fulltext index at [/oak:index/ntBaseLucene-2]
java.io.IOException: Invalid byte range request for [/oak:index/ntBaseLucene-2][_6l.cfs], position: 0, file length: -16, len: 1

and 

[async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.directory.CopyOnReadDirectory [/oak:index/ntBaseLucene-2] Found local copy for _6l.cfs in NIOFSDirectory@/<path>/repository/index/ntBaseLucene2-1612972365881/data lockFactory=NativeFSLockFactory@/<path>/repository/index/ntBaseLucene2-1612972365881/data but size of local 17266 differs from remote -16. Content would be read from remote file only  

Issue Links

• links to: PR