SOLR复制不断从master下载整个索引 [英] SOLR replication keeps downloading entire index from master
问题描述
我有2个奴隶从拥有17GB索引的主人复制。我将两个奴隶同步到此，之后我将轮询间隔设置为60秒。
I have 2 slaves replicating from a master that has a 17GB index. I synced both slaves to this, AFTER which I set the poll interval to 60 seconds.
其中一个奴隶试图下载整个17GB索引，即使只有很小一部分它已经改变了。另一个不这样做 - 它能够在没有这种强力同步的情况下获得最新的索引。冗余下载导致我超出了我的磁盘空间配额，因为下载17GB并且solr将第二次同步开始到另一个临时目录需要60多秒。
One of the slaves tries to download the entire 17GB index even if only a tiny portion of it has changed. The other does not do this - it is able to get the latest index without this brute force sync. The redundant downloading causes me to exceed my disk space quota because it takes more than 60 seconds to download 17GB and solr kicks off a 2nd sync into yet another temporary directory.
有没有关于如何调试这个的任何提示？
Does anyone have any tips on how to debug this?
推荐答案
我只能看到三个可能的原因：
I can only see three possible causes of this:
- 在时间间隔内触发优化，导致所有底层分段合并。请参阅：优化效果
- 您正在运行具有极高的合并因子导致您的索引与每个提交合并。请参阅：合并因子
- 您正在运行与compund文件。请参阅配置：
< useCompoundFile> false< / useCompoundFile>这也会在每次提交时导致段合并。
- An optimize is triggered during the time interval causing all of the underlying segmets to be merged. See: Optimize performance
- You're running with an exessivly high merge factor causing your index to merge with every commit. See: Merge factor
- You're running with compund files. See the config:
<useCompoundFile>false</useCompoundFile>This also causes a segment merge at every commit.
我能想到如何调试它的唯一方法是使用 Solr Replication HTTP API 。
The only way I can think of how to debug this is by manually makingt the replication with the Solr Replication HTTP API.
禁用复制并使用以下命令观察Solr master中文件的更新方式：
http：// host：port / solr / replication？command = indexversion
Disable the replication and watch how files are updated in the Solr master with the command:
http://host:port/solr/replication?command=indexversion
后跟：
http：// host：port / solr / replication？command = indexversion
希望这有帮助！
这篇关于SOLR复制不断从master下载整个索引的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
