well on the albums I add sometimes amazon puts the front picture as well as the back
yokel has quit
yvanzo
Oh, ok, it was ambiguous. If the release on MB has a cover art attached to it in the “Cover Art” tab, then Amazon front is not used.
razetime has quit
razetime joined the channel
If there is no image in the “Cover Art” tab, it is an issue. Either Amazon webservice is just unresponsive atm, or it is an MBS bug that should be reported.
yokel joined the channel
razetime
Hello
Leo_Verto, I have resubmitted the task
yokel has quit
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | Google Code-In https://goo.gl/8xSZem | Meeting agenda: Reviews, BB -> Docker (Leftmost), Graphs for all MetaBrainz projects (naiveai), next meeting (Freso)
yokel joined the channel
Slurpee joined the channel
yokel has quit
Freso
Leftmost, naiveai: What are the nature of your topics and how long do you expect them to be?
naiveai
I don't expect mine to be paritcularly long, it's just a question and some possible suggestions for charts
Maybe 10 min. at worst
Leftmost
I just want to kick off discussion of how to get BB shifted onto docker. Just figuring out how to build the channels of communication for shifting data and setting up config.
zas
yvanzo: is CAA-111 related to retry queue ? number of messages in retry queue doesn't seem to change much after you deployed the change
yvanzo, zas: I believe it's unrelated, the caa-redirect has no effect on the behavior of the caa-indexer, they don't communicate at all (and the split exception has been happening since before the queue started increasing)
retries happen when the indexer can't PUT something to S3 or can't fetch XML from our WS for example
my guess is it's related to recent failures of the IA's s3 service
yvanzo
There are both 500s and 503s in indexer logs.
dragonzeron has quit
bitmap
it's also likely that when our ws containers all had to be restarted the other day, the retry queue was increasing when they were generating all those 50x errors
because the indexer has to get XML from our WS to send to the IA
razetime has quit
zas
bitmap: is there a way to empty this queue ? or is it a problem on IA s3 service ?
I haven't been much active last week. Sickness got worse, so I had a couple of really bad days, and otherwise I've mostly been stressing about getting logistics in place for my move back to Scandinavia tomorrow. Still have a ton of things to do, so sorry if I'm quick on the trigger tonight. :/