The IA one? IA’s API is not "CAA API". And in a MeB context, certainly not "the" API. That said, I’d be interested in seeing the code you used.
2019-06-14 16511, 2019
CatQuest
hi Freso! `😺`
2019-06-14 16541, 2019
CatQuest
🐾😿
2019-06-14 16511, 2019
zas
solr cloud is still unstable :(
2019-06-14 16533, 2019
zas
it works somehow, but metrics show it isn't working as usual, response times are very bad, and each node exhibits different figures (load/disk activity/etc...), also there was a failure during 1 hour, but it seems to have partially recovered by itself...
2019-06-14 16541, 2019
ruaok
the failover is still disabled?
2019-06-14 16526, 2019
zas
nope, it's up, and working, though i switched to lb4 as master, and it seems to underperform compared to lb3, i may switch back again.
2019-06-14 16511, 2019
ruaok
but it didn't start randomly switching over during the last failure?
2019-06-14 16513, 2019
zas
the main issue was unsynced solr nodes, I just restarted them one by one, with proper delays and order
2019-06-14 16529, 2019
ruaok
what should I next steps be?
2019-06-14 16533, 2019
ruaok
*oour
2019-06-14 16536, 2019
zas
the random switching didn't happen, and the floating IP shouldn't float too much now
2019-06-14 16541, 2019
ruaok goes to make another coffee
2019-06-14 16549, 2019
zas
well, first, ensure the cloud is stable again
2019-06-14 16559, 2019
ruaok
so, the failover was a symptom of the instability?
2019-06-14 16505, 2019
zas
yes
2019-06-14 16527, 2019
zas
solr cloud stability is very tricky, in this regard one additional node might help
2019-06-14 16541, 2019
zas
if you don't restart them in the correct order and/or too fast, the whole thing enters in unstable state, keep trying to recover, sometimes succeeds, sometimes fails
2019-06-14 16500, 2019
ruaok
why do you think it is so unstable?
2019-06-14 16503, 2019
reosarevok
^ that sounds like Chernobyl again :p
2019-06-14 16547, 2019
zas
because numbers show it: not the same number of items in all replicas, not the same cpu/disk/network activity
2019-06-14 16557, 2019
zas
btw, response times are awful too
2019-06-14 16542, 2019
zas
I *think* it is recovering now, I manually rebooted each node, you have to always end with "leader" node (https://stats.metabrainz.org/d/T4MODrIiz/solr-clo… shows which one it is), if possible and let enough time between each node restart for them to sync with others
2019-06-14 16515, 2019
zas
in short, tricky stuff, that doesn't work as one could expect
2019-06-14 16527, 2019
zas
plus it's not totally dynamic (adding and/or removing nodes isn't trivial), read zookeeper/solr cloud docs if interested in details
2019-06-14 16527, 2019
zas
to ponder that, it works great most of the times
2019-06-14 16513, 2019
ruaok
and not running docker, right?
2019-06-14 16557, 2019
zas
nope, it's not really needed to add extra mess here ;)
ok, what can we do to automate the adding/removing of nodes?
2019-06-14 16523, 2019
ruaok
because even if capacity is NOT the issue, debugging a system near capacity makes everything much more difficult.
2019-06-14 16515, 2019
zas
automate ? well... start to read docs about solr cloud & zookeeper, you may soon understand why it isn't *that* easy. I have all what is needed to do it, but you have to understand that adding a node requires configuration changes on other nodes.
Freso, they're quite similar, although unfortunately using your own IA keys musicbrainz doesn't like.
2019-06-14 16532, 2019
zarcade_droid
Freso, a reply to your notes, I'm talking about the relationship on the releases, will add a link to the rest
2019-06-14 16557, 2019
Mr_Monkey
akhilesh: I've been looking at good ways to document the API and serve those docs. I quite like the idea of using inline JSDoc in the code (like we do for the rest of the projects) and have automatically serve documentation pages based on that.
Fancy giving it a go? It's the right moment to start documenting as you go, to avoid having to pay it back later :p
2019-06-14 16526, 2019
D4RK-PH0ENiX has quit
2019-06-14 16538, 2019
akhilesh
Mr_Monkey: I agree, but my target is to complete lookup request with tests then document the code as well as api endpoint for lookup request properly, try to get it merge, then move forward to browse requests. Is it fine to you?
2019-06-14 16522, 2019
Mr_Monkey
Yes, that's fine. Just thought I'd post this setup before I forget :)
2019-06-14 16530, 2019
iliekcomputers
ruaok: the messybrainz test failure seems like a Jenkins thing, I'll check.
2019-06-14 16508, 2019
ruaok
Thx
2019-06-14 16548, 2019
iliekcomputers
also, monies arrived, thanks! :)
2019-06-14 16542, 2019
ruaok
yeyaha,
2019-06-14 16510, 2019
D4RK-PH0ENiX joined the channel
2019-06-14 16541, 2019
Cyna
bitmap: I checked in another browser and facing the same result
2019-06-14 16538, 2019
Freso
zarcade_droid: Rule of thumb: don’t require editors to look up an entity’s links themselves; present it to them directly in the edit note. Both to make voters’ lives easier (less effort to check the edit) but also to lessen "bit rot": the links listed for a given entity may change over time, but the edit note is (actually) permanent. An entity may also get deleted (intentionally or by accident) in which case it is no longer
2019-06-14 16538, 2019
Freso
possible to look up relationships, but the edits are still in the system, so someone may still come across the edit and want to double check it.
2019-06-14 16535, 2019
Freso
zarcade_droid: And the "API" for uploading to CAA is: https://musicbrainz.org/release/$MBID/add-cover-a… – anything else is unsupported. (I’d still like to see your code though. In general, it’s a good idea to disclose in edit notes when doing tool assisted edits, including a source to the tool.)
2019-06-14 16542, 2019
zarcade_droid
Freso, yeah, adding the link to the edits now but if the relationship is removed from the original then probably for a good reason and the one in the edit will also be useless, but shrug, if it helps to vote on the cover art I'm adding it
2019-06-14 16511, 2019
rsh7 joined the channel
2019-06-14 16511, 2019
Freso
It won’t be useless: it will tell what the source of the image was.
2019-06-14 16547, 2019
zarcade_droid
*was*
2019-06-14 16553, 2019
Freso
If that’s no longer considered a good source, then that might be an argument for removing the image. (Probably not on these cases.)
2019-06-14 16511, 2019
zarcade_droid
There's also the API endpoint "https://musicbrainz.org/ws/js/cover-art-upload/"
2019-06-14 16541, 2019
Freso
That’s an internal API that isn’t supported for others.
2019-06-14 16511, 2019
Freso
ws/2/* is the only supported API.
2019-06-14 16552, 2019
zarcade_droid
Given that the APIs aren't officially supported, I'm wary of providing any source
Freso, there's also the licensing, lack of comments and requirement to run scripts in a certain order with s***load of manual work to get the artists linked
2019-06-14 16523, 2019
zarcade_droid
so like, if you're interested in a certain component I can share that but it has no value for anyone else
2019-06-14 16512, 2019
rcombs
so, is the new search stuff ready to deploy yet, and is there any documentation on how to keep the indexes up-to-date?
2019-06-14 16556, 2019
ruaok
rcombs: yvanzo is the person to help you with that
2019-06-14 16507, 2019
rcombs
yvanzo: ohai
2019-06-14 16526, 2019
zarcade_droid
(just to separate questions nicely) a) What could be done to get bigfinish.com URLs normalized, type autodetected and displayed on the sidebar?
2019-06-14 16514, 2019
zarcade_droid
b) Release medium without tracks is probably soon doable - now comes the next step from it, would it be possible to do works related to a medium instead of a track?
