Closed asdf23 closed 2 years ago
Thank you for your report, yes, these messages should not have been logged. This has no impact on anything else than the output of the vespa-route
tool.
docker exec -it vespa bash
[root@vespa-container /]# vespa-route
[2022-04-22 08:05:11.426328] 2113/48242 (.documenttyperepo) info: applying new doc type config
[2022-04-22 08:05:11.426517] 2113/48242 (.documenttyperepo) info: doc document
[2022-04-22 08:05:11.426543] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10000
[2022-04-22 08:05:11.426590] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10001
[2022-04-22 08:05:11.426635] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10009
[2022-04-22 08:05:11.426662] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10002
[2022-04-22 08:05:11.426710] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10003
[2022-04-22 08:05:11.426732] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10004
[2022-04-22 08:05:11.426753] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10005
[2022-04-22 08:05:11.426801] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10006
[2022-04-22 08:05:11.426820] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10007
[2022-04-22 08:05:11.426837] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10008
[2022-04-22 08:05:11.426855] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10010
[2022-04-22 08:05:11.426916] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10011
[2022-04-22 08:05:11.427029] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10012
[2022-04-22 08:05:11.427051] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10014
[2022-04-22 08:05:11.427074] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10013
[2022-04-22 08:05:11.427093] 2113/48242 (.documenttyperepo) info: doc track
[2022-04-22 08:05:11.427112] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10015
[2022-04-22 08:05:11.427126] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10016
[2022-04-22 08:05:11.427146] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10018
[2022-04-22 08:05:11.427168] 2113/48242 (.documenttyperepo) info: ensure indexes: add 10017
[2022-04-22 08:05:11.427323] 2113/48242 (.documenttyperepo) info: retry complex types, 0 missing
[2022-04-22 08:05:11.527203] 2113/27696 (.slobrok.mirror) info: successfully connected to location broker tcp/vespa-container:19099 (mirror initialized with 9 service names)
There are 6 route(s):
1. default
2. default-get
3. storage/cluster.tracks
4. tracks
5. tracks-direct
6. tracks-index
There are 2 hop(s):
1. default/chain.indexing
2. indexing
@arnej27959 should the slobrok.mirror message be silenced too ?
@arnej27959 should the slobrok.mirror message be silenced too ?
yes and no :-( we have had problems some months ago and added the mirror logging to see if we could understand what was going on. so we want to keep it as-is for that. but we want to make it debug level at some point.
OK, Present in 7.577.4 and on
after preforming an upgrade:
yum install vespa-7.574.71
./vespa-route --services