#metabrainz

/

      • zas
        hey samj1912
      • 2018-12-14 34802, 2018

      • samj1912
        Hey o/
      • 2018-12-14 34805, 2018

      • zas
        not much issues with new search, it performs well enough, but we lack of cpu power on peak times
      • 2018-12-14 34823, 2018

      • zas
        that's more an issue with hetzner cloud performance
      • 2018-12-14 34847, 2018

      • samj1912
        It's still on 4 machines?
      • 2018-12-14 34832, 2018

      • zas
        apart that, i need you to upgrade solr, because it's blocking the next step to the drop of ws/1 (current solr version has security vulnerabilites, so we can't open to public yet)
      • 2018-12-14 34848, 2018

      • zas
        yes, 4 nodes + 2 haproxy
      • 2018-12-14 34805, 2018

      • samj1912
        Upgrade solr as in?
      • 2018-12-14 34808, 2018

      • zas
        performance is still better than old search though ;)
      • 2018-12-14 34814, 2018

      • zas
        solr version
      • 2018-12-14 34821, 2018

      • samj1912
        Ah to 7.5?
      • 2018-12-14 34849, 2018

      • zas
        to the most recent one, afaik we didn't because of some issues, prolly with mbsssss, dunno
      • 2018-12-14 34804, 2018

      • samj1912
        I'll look into it
      • 2018-12-14 34806, 2018

      • zas
        solr search peak around ~160 req/s with response time <300ms
      • 2018-12-14 34820, 2018

      • samj1912
        Nice!
      • 2018-12-14 34806, 2018

      • zas
        we are cpu-bounded, and hetzner cloud machines have variable cpu power... so performance varies, it works good enough for now though
      • 2018-12-14 34809, 2018

      • zas
        in best cases we go down to 60ms response time when load is low
      • 2018-12-14 34810, 2018

      • samj1912
        zas: what was the name of the test vm that we had for solr tests?
      • 2018-12-14 34841, 2018

      • samj1912
        nvm
      • 2018-12-14 34843, 2018

      • samj1912
        found it
      • 2018-12-14 34855, 2018

      • george
        Wait you can have profile pictures on IRC? 🤔
      • 2018-12-14 34801, 2018

      • samj1912
        yeah :P
      • 2018-12-14 34810, 2018

      • samj1912
        If you use irccloud
      • 2018-12-14 34812, 2018

      • samj1912
        zas: you around?
      • 2018-12-14 34827, 2018

      • zas
        yep
      • 2018-12-14 34836, 2018

      • samj1912
        I synced the deps properly
      • 2018-12-14 34850, 2018

      • samj1912
        pushing out the new solr ver of mb-solr
      • 2018-12-14 34845, 2018

      • george
        Ooo cool
      • 2018-12-14 34826, 2018

      • samj1912
        the next time you want to do so
      • 2018-12-14 34833, 2018

      • samj1912
        simply download the latest solr form the website
      • 2018-12-14 34838, 2018

      • samj1912
        do a find for all the jars
      • 2018-12-14 34848, 2018

      • samj1912
        and update the relevant versions in pom.xml inside mb-solr
      • 2018-12-14 34800, 2018

      • zas
        but the deployment does'nt rely on mb-solr (do i miss something?) https://github.com/metabrainz/mb-solr-cloud
      • 2018-12-14 34831, 2018

      • samj1912
        it does right?
      • 2018-12-14 34836, 2018

      • samj1912
        it gets the jar?
      • 2018-12-14 34814, 2018

      • samj1912
      • 2018-12-14 34800, 2018

      • zas
        ah yes
      • 2018-12-14 34815, 2018

      • zas
      • 2018-12-14 34825, 2018

      • samj1912
        yes
      • 2018-12-14 34836, 2018

      • samj1912
        I updated both to 7.5.0
      • 2018-12-14 34840, 2018

      • samj1912
        see the test branch on mb-solr
      • 2018-12-14 34843, 2018

      • samj1912
        building out a new jar
      • 2018-12-14 34850, 2018

      • samj1912
        and testing on mb-solr-test
      • 2018-12-14 34808, 2018

      • zas
        can we deploy nodes by nodes ? i mean if we upgrade one node, is the solr cloud supposed to handle it ?
      • 2018-12-14 34818, 2018

      • samj1912
        hmm
      • 2018-12-14 34820, 2018

      • samj1912
        not sure
      • 2018-12-14 34822, 2018

      • samj1912
        it should
      • 2018-12-14 34835, 2018

      • samj1912
        ah yes it should
      • 2018-12-14 34817, 2018

      • zas
        i hope so; but i'll be ready to shut down all if it goes wrong, so we need to proceed on low activity times (in european morning)
      • 2018-12-14 34833, 2018

      • samj1912
        cool
      • 2018-12-14 34847, 2018

      • Kapish joined the channel
      • 2018-12-14 34852, 2018

      • samj1912
        at worse you can just bring a node down
      • 2018-12-14 34855, 2018

      • samj1912
        and revert
      • 2018-12-14 34800, 2018

      • zas
        yes
      • 2018-12-14 34845, 2018

      • zas
        i'll be busy this weekend, but i'll give it a try monday morning
      • 2018-12-14 34803, 2018

      • zas
        about picard, we are about to release 2.1, outsidecontext and i think we are almost done, still few minor issues to solve before release, but overall it looks good, it should happen next week
      • 2018-12-14 34828, 2018

      • samj1912
        nice :D
      • 2018-12-14 34856, 2018

      • jwf
        george: You can also have profile pictures with Matrix. :-) https://opensource.com/article/17/5/introducing-r…
      • 2018-12-14 34846, 2018

      • jwf
        ruaok++
      • 2018-12-14 34858, 2018

      • jwf
        ruaok: Annual report looks great. I left a comment with one question I had
      • 2018-12-14 34816, 2018

      • Kapish
        Freso i was planning to make a presentation on MB
      • 2018-12-14 34828, 2018

      • Kapish
        i need your help with that
      • 2018-12-14 34841, 2018

      • jwf
        Nice work and efforts by the MeB team in 2017. Even with the hiccups, it looks like it was an eventful year and I got a better picture to how things are ticking
      • 2018-12-14 34846, 2018

      • jwf
        I appreciate the transparency
      • 2018-12-14 34856, 2018

      • samj1912
      • 2018-12-14 34800, 2018

      • samj1912
        it works
      • 2018-12-14 34850, 2018

      • zas
        good :) thanks !
      • 2018-12-14 34803, 2018

      • zas
        can you provide a PR for mb-solr-cloud ? i'll merge and attempt a deployment on monday
      • 2018-12-14 34811, 2018

      • samj1912
        yeah
      • 2018-12-14 34810, 2018

      • samj1912
        I updated the docker images
      • 2018-12-14 34822, 2018

      • samj1912
        in case you ever want to test it on queen again
      • 2018-12-14 34853, 2018

      • samj1912
      • 2018-12-14 34858, 2018

      • samj1912
      • 2018-12-14 34827, 2018

      • samj1912
        have fun ;)
      • 2018-12-14 34853, 2018

      • samj1912
        Also, I might be giving a talk on solr this fosdem if it gets accepted :D
      • 2018-12-14 34809, 2018

      • samj1912
        Let me know if any of you peeps are there
      • 2018-12-14 34800, 2018

      • ruaok
        jwf: bad copypasta. that column is the user privs column from the DB. I need to remove it.
      • 2018-12-14 34808, 2018

      • ruaok
        fxied.
      • 2018-12-14 34816, 2018

      • ruaok
        reosarevok: take a look, please?
      • 2018-12-14 34847, 2018

      • reosarevok
        Oh no
      • 2018-12-14 34819, 2018

      • reosarevok takes a look to try to figure out what he needs to take a look at
      • 2018-12-14 34805, 2018

      • reosarevok
        Ok, I have a Wikimedia event starting soon (well 20 min ago, but :p) but I should find some time to read that while there
      • 2018-12-14 34818, 2018

      • ruaok
        no rush.
      • 2018-12-14 34805, 2018

      • Kapish has quit
      • 2018-12-14 34841, 2018

      • Mineo
        ruaok or zas: the wikidata bot still hasn't made it past areas :-( can one of you do a `SELECT count(*) FROM bot_wikidata_area_processed;` on the `wikidata_bot_db`? I'm curious what the difference between that number and the number of area-wiki* relationships (~110k) is
      • 2018-12-14 34848, 2018

      • ruaok
        k
      • 2018-12-14 34805, 2018

      • ruaok
        21914
      • 2018-12-14 34819, 2018

      • reosarevok
        That's... not a lot
      • 2018-12-14 34836, 2018

      • ruaok
        given how long its been running, it smells like a bug
      • 2018-12-14 34838, 2018

      • reosarevok
        Think so, yeah
      • 2018-12-14 34854, 2018

      • reosarevok
        My bots go through that many entries in a few days tops
      • 2018-12-14 34813, 2018

      • reosarevok
        (different sources etc, but I assume the delay is connected to WD not MB)
      • 2018-12-14 34829, 2018

      • ruaok
        reosarevok: I just gave you write access to the doc.
      • 2018-12-14 34834, 2018

      • ruaok
        reload and just make the changes.
      • 2018-12-14 34852, 2018

      • Mineo
        ouch, that number is unexpectedly low. if there's time (doesn't have to be today), could someone send me a snippet of the logs? the bot is usually very chatty
      • 2018-12-14 34807, 2018

      • ruaok
        very chatty == will take a moment.
      • 2018-12-14 34819, 2018

      • ruaok
        getting logs out of docker is a pain.
      • 2018-12-14 34837, 2018

      • ruaok
        hmm.
      • 2018-12-14 34844, 2018

      • ruaok
        1.5GB uncompressed so far.
      • 2018-12-14 34852, 2018

      • alastairp
        yeah, I really want to fix docker logging on our setup too
      • 2018-12-14 34811, 2018

      • alastairp
        I kind of thing the best way is to have a centralised logging server, but that seems annoying to set up :(
      • 2018-12-14 34839, 2018

      • ruaok
        so annoying that we've not managed it in 2 years.
      • 2018-12-14 34839, 2018

      • reosarevok
        ruaok: ok
      • 2018-12-14 34849, 2018

      • reosarevok
        I'd like to see the logs too if possible
      • 2018-12-14 34829, 2018

      • ruaok
        I'll publish it once the xz finishes.
      • 2018-12-14 34834, 2018

      • ruaok
        could be a while still.
      • 2018-12-14 34814, 2018

      • ruaok
        huh?
      • 2018-12-14 34829, 2018

      • ruaok
        651k. Down from 1.5g.
      • 2018-12-14 34839, 2018

      • ruaok bows down before xz
      • 2018-12-14 34843, 2018

      • outsidecontext has quit
      • 2018-12-14 34804, 2018

      • ruaok
        emailed to reo and Mineo
      • 2018-12-14 34829, 2018

      • Mineo
        thanks
      • 2018-12-14 34805, 2018

      • jwf
        ruaok: Ah. All good! :+1:
      • 2018-12-14 34852, 2018

      • reosarevok
        ruaok: "The silver and gold supporter categories picked up in 2016; also we gave up on the mobile tier in 2016" 2017 I assume but confirm
      • 2018-12-14 34807, 2018

      • ruaok
        yeah
      • 2018-12-14 34859, 2018

      • reosarevok
        ruaok: seems pretty good in general, changed a few things
      • 2018-12-14 34810, 2018

      • ruaok
        thank you!
      • 2018-12-14 34850, 2018

      • pulkit6559 joined the channel
      • 2018-12-14 34837, 2018

      • pulkit6559 has quit
      • 2018-12-14 34859, 2018

      • github joined the channel
      • 2018-12-14 34859, 2018

      • github
        [picard-plugins] phw closed pull request #189: Add format_performer_tags plugin (2.0...2.0) https://git.io/fpbto
      • 2018-12-14 34859, 2018

      • github has left the channel
      • 2018-12-14 34811, 2018

      • michelv has quit
      • 2018-12-14 34814, 2018

      • Slurpee has quit
      • 2018-12-14 34810, 2018

      • github joined the channel
      • 2018-12-14 34810, 2018

      • github
        [picard-plugins] rdswift opened pull request #190: Add UI changes by outsidecontext / phw (2.0...2.0) https://git.io/fpbGG
      • 2018-12-14 34810, 2018

      • github has left the channel
      • 2018-12-14 34814, 2018

      • Kapish joined the channel
      • 2018-12-14 34850, 2018

      • Kapish has quit
      • 2018-12-14 34836, 2018

      • wagu joined the channel
      • 2018-12-14 34821, 2018

      • wagu
        howdy, I have a local Musicbrainz server setup and trying to run an import from a dump
      • 2018-12-14 34824, 2018

      • wagu
        e.g. ./admin/InitDb.pl --createdb --import /tmp/dumps/mbdump*.tar.bz2 --echo
      • 2018-12-14 34839, 2018

      • wagu
        but that command gives me an error: Can't locate JSON.pm in @INC (you may need to install the JSON module)
      • 2018-12-14 34837, 2018

      • wagu
        is this expected? I followed instructions from https://musicbrainz.org/doc/MusicBrainz_Server/Se… to setup and don't think I did anything weird
      • 2018-12-14 34838, 2018

      • yvanzo
        hi wagu, did you install Perl dependencies by following https://github.com/metabrainz/musicbrainz-server/…
      • 2018-12-14 34857, 2018

      • wagu
        @yvanzo: I did not, but assumed that was done as part of https://musicbrainz.org/doc/MusicBrainz_Server/Se…
      • 2018-12-14 34806, 2018

      • wagu
        am I wrong? I thought this was a prebuilt server
      • 2018-12-14 34855, 2018

      • yvanzo
        wagu: oh, you mean you installed the VM?
      • 2018-12-14 34859, 2018

      • wagu
        yes
      • 2018-12-14 34828, 2018

      • wagu
        and I do see perl dependencies I think in ~/perl5/lib/perl5 so pretty sure they exist
      • 2018-12-14 34855, 2018

      • yvanzo
        Ok, that might be an environment issue.
      • 2018-12-14 34826, 2018

      • wagu
        what do you mean?
      • 2018-12-14 34854, 2018

      • yvanzo
        You need to set environment for running Perl command with: eval $( perl -Mlocal::lib )
      • 2018-12-14 34825, 2018

      • wagu
        @yvanzo: ah thanks so much! that works
      • 2018-12-14 34849, 2018

      • Slurpee joined the channel
      • 2018-12-14 34849, 2018

      • Slurpee has quit
      • 2018-12-14 34849, 2018

      • Slurpee joined the channel
      • 2018-12-14 34845, 2018

      • Zialus_PT has quit