如何解决solr indexupgrader无法找到_md6.si?

发布于 2025-02-13 17:28:28 字数 1640 浏览 1 评论 0原文

我正在尝试将Solr 4.X索引升级到Solr 5.X(因此我可以将其一直升级到8.x)。 SOLR安装本身是版本4.5.1。

indexupgradertool抱怨说,它在我的索引中找不到文件_md6.si。它在我们的任何索引中都不存在,也没有有关Internet上文件的信息。我在所有索引文件中尝试了文本搜索,认为这可能是一种断开的链接,但我也无法那样找到它。

堆栈在下面。有人知道会出问题吗?

Exception in thread "main" java.nio.file.NoSuchFileException: C:\Temp\Dev_feature\default\index\_md6.si
        at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
        at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
        at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
        at sun.nio.fs.WindowsFileSystemProvider.newFileChannel(Unknown Source)
        at java.nio.channels.FileChannel.open(Unknown Source)
        at java.nio.channels.FileChannel.open(Unknown Source)
        at org.apache.lucene.store.MMapDirectory.openInput(MMapDirectory.java:196)
        at org.apache.lucene.codecs.lucene40.Lucene40SegmentInfoReader.read(Lucene40SegmentInfoReader.java:51)
        at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:361)
        at org.apache.lucene.index.SegmentInfos$1.doBody(SegmentInfos.java:457)
        at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:912)
        at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:758)
        at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:453)
        at org.apache.lucene.index.DirectoryReader.listCommits(DirectoryReader.java:277)
        at org.apache.lucene.index.IndexUpgrader.upgrade(IndexUpgrader.java:151)
        at org.apache.lucene.index.IndexUpgrader.main(IndexUpgrader.java:74)

I'm trying to upgrade a Solr 4.x index to Solr 5.x (so I can upgrade it all the way to 8.x). The Solr installation itself is version 4.5.1.

The IndexUpgraderTool complains that it can't find the file _md6.si in my index. It doesn't exist in any of our indexes, and there is no information about the file on the internet. I tried a text search inside all of the index files, thinking it might be a broken link of sorts, but I wasn't able to find it that way either.

The stacktrace is below. Does anyone have any idea what could be wrong?

Exception in thread "main" java.nio.file.NoSuchFileException: C:\Temp\Dev_feature\default\index\_md6.si
        at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
        at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
        at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
        at sun.nio.fs.WindowsFileSystemProvider.newFileChannel(Unknown Source)
        at java.nio.channels.FileChannel.open(Unknown Source)
        at java.nio.channels.FileChannel.open(Unknown Source)
        at org.apache.lucene.store.MMapDirectory.openInput(MMapDirectory.java:196)
        at org.apache.lucene.codecs.lucene40.Lucene40SegmentInfoReader.read(Lucene40SegmentInfoReader.java:51)
        at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:361)
        at org.apache.lucene.index.SegmentInfos$1.doBody(SegmentInfos.java:457)
        at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:912)
        at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:758)
        at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:453)
        at org.apache.lucene.index.DirectoryReader.listCommits(DirectoryReader.java:277)
        at org.apache.lucene.index.IndexUpgrader.upgrade(IndexUpgrader.java:151)
        at org.apache.lucene.index.IndexUpgrader.main(IndexUpgrader.java:74)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

音盲 2025-02-20 17:28:28

在运行索引升级器之前,在索引上进行优化总是一个好主意 - 这样,您将获得索引升级器可以使用的干净索引。索引文件将被合并并重写为单个索引,并将删除任何遗留的删除文档等。

通常,您可以通过向更新处理程序发出“优化命令”来调用优化:

/update?optimize=true

It's always a good idea to run optimize on the index before running index upgrader - that way you'll get a clean index that the index upgrader can work with. The index files will be merged and rewritten as a single index, and any lingering deleted documents, etc. will be removed.

You can generally call optimize by issuing an optimize command to the update handler:

/update?optimize=true
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文