Vespa content node search threads not reflecting in vespa-get-config

user_8179207 0
Viewed 33

After configuring application package with:

    <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

The change is not being reflected when: vespa-get-config -n vespa.config.search.core.proton | grep search, the output is:

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?

vespa
1 Answers

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.

user_87142350
Related