[英]Vespa content node search threads not reflecting in vespa-get-config
After configuring application package with:使用以下命令配置应用程序 package 后:
<proton>
<tuning>
<searchnode>
<requestthreads>
<search>88</search>
<persearch>4</persearch>
</requestthreads>
</searchnode>
</tuning>
</proton>
And app package activation requests searchnode restart due to: Num searcher threads\nproton.numsearcherthreads has changed
并且应用 package 激活请求 searchnode 重新启动,原因是:
Num searcher threads\nproton.numsearcherthreads has changed
The change is not being reflected when: vespa-get-config -n vespa.config.search.core.proton | grep search
在以下情况下未反映更改:
vespa-get-config -n vespa.config.search.core.proton | grep search
vespa-get-config -n vespa.config.search.core.proton | grep search
, the output is: vespa-get-config -n vespa.config.search.core.proton | grep search
,output 为:
search.mmap.advise "NORMAL"
search.memory.limiter.maxthreads 0
search.memory.limiter.mincoverage 1
search.memory.limiter.minhits 1000000
numsearcherthreads 64
numthreadspersearch 1
distribution.searchablecopies 1
Is this a bug?这是一个错误吗? where can it be validated that the threads being used are indeed what was configured?
在哪里可以验证正在使用的线程确实是配置的?
Changing thread counts is a change that requires a restart of the searchnode process - the prepare/deploy feedback will tell you which services needs to be restarted.更改线程数是需要重新启动 searchnode 进程的更改 - 准备/部署反馈将告诉您哪些服务需要重新启动。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.