reosarevok: to bring more accuracy for the next day
reosarevok
Do see if my suggestion in the ticket seems good enough maybe :)
yvanzo
reosarevok: the WIP commit is supposed to fix the first commit (of PR #1112) or that is more complicated?
reosarevok
I think it should just fix the first commit to work with the editor data changes
(I wrote this a while ago, but that's what it looked like on review + test)
zas
yvanzo: I wonder why solr nodes have that much load when SIR is working, I guess that's related to Indexes replication, but it seems a lot of load for few changes
mb-solr-5 is writing to disk at a permanent rate of 600mb/s ... other nodes < 30mb/s, any idea?
atj
the graph shows it's reading from disk at 600MB/s?
is the CPU usage user mode usage or non-idle?
zas
yes, sorry s/write/read/
user
atj
some nice graphs there zas, did you create the dashboard?
zas
yes
atj
I do enjoy creating a Grafana dashboard :)
zas
I'll stop this instance, and see how the cluster acts
atj: that's a very good monitoring tool, especially since they added alerts
atj
yeah it's very useful for operational monitoring. I think the alerting functionality is a bit weak though as you can't use templated graphs.
quite strange how the disk read on solr-5 seems to be the only outlier
zas
yes... I'd more than strange ;)
ok stopped this solr instance, let's see if other nodes exhibits same behavior
it doesn't seem another node started to read at this rate, in fact, apart a bit more handled queries (4 nodes instead of 5) nothing changed
I'll start it again
rebooting the node while at it
alastairp
deploying new LB
Etua joined the channel
BrainzGit
[listenbrainz-server] paramsingh opened pull request #1309 (master…param-user-recommendation-event-table): Add new table for user recommendation events https://github.com/metabrainz/listenbrainz-serv...
seems that it didn't rename it from mbid_mapping_20210302_041458 to mbid_mapping
ruaok
there is a concept of collection aliases. there is an alias from mbid_mapping to mbid_mapping_20210302_041458. Changing this alias allows the atomic rotating of indexes.
this problem is a connection problem first and foremost. the config info that LB labs has is correct, but the container cannot reach typesense.
I'll just commit the fix directly to master. should I push v-2021-03-02.1 ?
alastairp
just do the commit, _lucifer can do the release + push :)
ruaok
commit pushed.
thanks _lucifer
alastairp
it'll be 02.0, I released yesterday's build
_lucifer
on it
alastairp
_lucifer: git tag v-2021-03-02.1, merge master to production, make github release, build+push image
uh
v-2021-03-02.0
I'm really not a fan of magic python HTTP API wrappers that hide the details of the request that it's making. all such clients should have a straightforward way of debugging the details of the requests
ruaok
"magic python HTTP API wrappers" like what?
alastairp
like the typesense client library
I call client.collections['foo'].documents.search, but what http request is that actually making
I ran into exactly the same problem with another client yesterday. Once I could work out what query it was trying to make, the problem was obvious, but it took ages to get to that point