/srv/irclogs.ubuntu.com/2009/12/03/#launchpad-meeting.txt

=== salgado-afk is now known as salgado
=== jelmer_ is now known as jelmer
=== mrevell is now known as mrevell-lunch
=== statik` is now known as statik
=== mrevell-lunch is now known as mrevell
=== danilo_ is now known as danilos
matsubara#startmeeting15:04
MootBotMeeting started at 09:04. The chair is matsubara.15:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:04
matsubaraWelcome to this week's Launchpad Production Meeting. For the next 45 minutes or so, we'll be coordinating the resolution of specific Launchpad bugs and issues.15:04
sinzuime15:04
matsubara[TOPIC] Roll Call15:04
MootBotNew Topic:  Roll Call15:04
allenapme15:04
matsubarasorry for being late, I was on my stand up meeting15:04
matsubarastub, Chex, gary_poster, rockstar, bigjools, danilo_: Hi15:05
gary_postermatsubara: hi15:05
danilosme15:05
bigjoolsmatsubara: TLs are in a call.... :/15:05
bigjoolsnoodles775: can you cover me please?15:05
noodles775bigjools: OK.15:05
matsubarabigjools, right, by the end of this meeting sinzui will propose a change for the production meeting so it won't clash anymore15:05
bigjoolsta15:05
danilosbigjools, we've got an agenda item to move the call, so you should be in for at least that15:05
matsubaraok, so let's move on. Chex, rockstar and stub can join in later15:07
matsubara[TOPIC] Agenda15:08
matsubara * Actions from last meeting15:08
matsubara * Oops report & Critical Bugs & Broken scripts15:08
matsubara * Operations report (mthaddon/Chex/spm/mbarnett)15:08
matsubara * DBA report (stub)15:08
MootBotNew Topic:  Agenda15:08
matsubara * Proposed items15:08
matsubara[TOPIC] * Actions from last meeting15:08
MootBotNew Topic:  * Actions from last meeting15:08
matsubara* Ursinha to send one email to lp list explaining the qa-tags experiment15:08
matsubara* matsubara to chase someone from code team about bug 48000015:08
matsubara* matsubara to chase code people about code script failures (create-merge-proposals, branch puller and update branches)15:08
matsubara* matsubara to ask someone from code about bug 48531815:08
matsubara    * emailed tim about these15:08
matsubara* Chex to follow up with thumper about the multiple git import failures on the importd15:08
matsubara* matsubara to file a bug for OOPS-1420ED104715:08
matsubara    * there was a bug filed for this already. Bug 48436815:08
matsubara* sinzui to investigate failure on the mirror prober (The script 'distributionmirror-prober' didn't run on 'loganberry' between 2009-11-23 06:07:04 and 2009-11-23 12:07:04 (last seen 2009-11-23 04:54:10.444057))15:08
ubottuLaunchpad bug 480000 in launchpad-code "OOPS deleting a branch" [Low,Triaged] https://launchpad.net/bugs/48000015:08
matsubara* matsubara to ask gary about python2.5 update and get back to losas15:08
matsubara    * francis emailed the list and gary about this15:08
matsubara* matsubara to ask stub to contact losas about load increase on wildcherry15:08
ubottuLaunchpad bug 485318 in launchpad-code "POSTToNonCanonicalURL error using bazaar client" [Wishlist,Triaged] https://launchpad.net/bugs/48531815:08
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1420ED104715:08
matsubara    * emailed stub about this one15:08
ubottuLaunchpad bug 484368 in rosetta "LocationError: 'top_projects_and_packages_to_translate'" [High,Triaged] https://launchpad.net/bugs/48436815:08
matsubaraI don't recall an email explaining the qa-tags experiment but Ursula did show up a wiki page for me before leaving on vacation15:09
sinzuimatsubara: the script was dealyed, ran fine later. The same thing happened to the PRF. it is running fine15:09
matsubaradanilo_, do you know if that email was done?15:09
matsubarasinzui, thanks for checking15:09
matsubaras/done/sent/15:09
=== salgado is now known as salgado-lunch
matsubaramthaddon, around?15:11
matsubaraI guess people are too busy with other stuff15:12
matsubaralet's move on15:12
matsubara[action] * Ursinha to send one email to lp list explaining the qa-tags experiment15:12
MootBotACTION received:  * Ursinha to send one email to lp list explaining the qa-tags experiment15:12
matsubara[action] * Chex to follow up with thumper about the multiple git import failures on the importd15:12
MootBotACTION received:  * Chex to follow up with thumper about the multiple git import failures on the importd15:12
matsubara[TOPIC] * Oops report & Critical Bugs & Broken scripts15:13
MootBotNew Topic:  * Oops report & Critical Bugs & Broken scripts15:13
matsubaradanilo_,  is https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1425EA795 and https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1429EB593 related to bug https://bugs.edge.launchpad.net/rosetta/+bug/484368?15:13
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1425EA79515:13
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1429EB59315:13
ubottuUbuntu bug 484368 in rosetta "LocationError: 'top_projects_and_packages_to_translate'" [High,Triaged]15:13
matsubarasinzui, https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1430F257415:14
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1430F257415:14
matsubarasinzui, is this registry or foundations?15:14
sinzuifoundations15:14
sinzuimatsubara: high/critical15:14
sinzuimatsubara: This may be caused by the replication delay15:15
matsubaraall right. I'll file a bug for it and ask gary_poster to take a look15:15
matsubara[action] matsubara to file a high/critical bug for OOPS-1430F257415:15
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1430F257415:15
MootBotACTION received:  matsubara to file a high/critical bug for OOPS-1430F257415:15
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1430F257415:15
matsubararockstar, https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1427EA45 I've seen 4 occurrences of this oops last week, is this a known issue? some bad data? worth a bug?15:16
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1427EA4515:16
matsubarahttps://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1426EC1536 shouldn't this one be a NotFound rather than a NotFoundError?15:16
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1426EC153615:16
matsubaraI guess I'll have to email tim about those as well15:16
gary_posterOOPS-1430F2574 : I agree that this is probably replication15:16
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1430F257415:16
matsubara[action] matsubara to email tim about https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1427EA45 I've seen 4 occurrences of this oops last week, is this a known issue? some bad data? worth a bug?15:16
matsubara<matsubara> https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1426EC1536 shouldn't this one be a NotFound rather than a NotFoundError?15:16
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1427EA4515:16
MootBotACTION received:  matsubara to email tim about https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1427EA45 I've seen 4 occurrences of this oops last week, is this a known issue? some bad data? worth a bug?15:16
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1426EC153615:16
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1427EA4515:16
matsubaradamn15:16
matsubara[action] matsubara to email tim about https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1426EC1536  shouldn't this one be a NotFound rather than a NotFoundError?15:17
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1426EC153615:17
MootBotACTION received:  matsubara to email tim about https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1426EC1536  shouldn't this one be a NotFound rather than a NotFoundError?15:17
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1426EC153615:17
matsubarawe have 5 critical bugs, 4 of them fix committed and 1 in progress15:18
matsubaraso all good in that area15:18
matsubarano script failures since last week (well, only PRF but that's fine per sinzui)15:19
matsubara[TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)15:20
MootBotNew Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)15:20
matsubaralet's move to the next topic as there's no losa around15:21
matsubara[TOPIC] * DBA report (stub)15:21
MootBotNew Topic:  * DBA report (stub)15:21
stubWe have had two incidents where appserver requests have sent the load on the main database server over 100 in some sort of a feedback loop we dubbed the DB Death Spiral. We think we tracked down the trigger - the page the load balancers used to detect if Launchpad is up accessed the session database, and our session machinery becomes a bottleneck under load.15:21
stubWhat we hope is the immediate fix lands tomorrow - stopping that page from accessing the database. I have plans of offloading the bulk of the session machinery work to memcache so it should stop becoming a bottleneck under load, but that is work for the next cycle or two.15:22
stubWe also managed to have replication issues, because when it rains it pours. Both times where do do with adding a new replica into the cluster.15:22
stubThe first time, it turned out some events where left around that should have been cleared up causing conflicts. So when one of our replicas tried to confirm it had seen an event, it found the confirmation was already there so it aborted.15:22
stubThe second one, today, removing the replica from the cluster hadn't quite succeeded so replication lag on the cluster was increasing. This wasn't noticed or was ignored, and we attempted to re-add the database back into a heavily lagged cluster. This needed recovering. I don't think users where affected today.15:22
stubAnd that is all I've typed so far ;)15:23
matsubarastub, should I expect to see lots of OOPSes in the reports about this replication lag issue?15:24
stubI've got a bug open to add some more safety belts to our helpers to catch these cases.15:24
stubmatsubara: Hopefully not. I'm not sure though.15:24
matsubarastub, all right. I'll let you know if spot anything15:25
matsubarathanks stub15:25
matsubara[TOPIC] * Proposed items15:25
MootBotNew Topic:  * Proposed items15:25
matsubara# Move the production meeting one hour later to avoid clash with other meetings (sinzui)15:26
sinzuiplease15:26
sinzuiI am in another meeting right now15:26
matsubaraI'm +1 on the change. it'd be actually better for me to have the meeting at 16UTC15:26
matsubarahow about the others?15:26
noodles775I'm assuming that bigjools is also +1 for the same reason.15:27
matsubaraand danilo too15:27
bigjools+115:27
sinzui+115:28
stubThat is getting nuts for me, but I can do the report by email just as easily as typing it up here.15:28
matsubaraon the other hand, what do you think about not having this meeting at all anymore? do you think it's useful or the format could be changed? I see lots of people missing this meeting or not paying much attention...15:28
matsubarastub, your section and the losas section are the ones that interest me the most :-)15:29
matsubarastub, reports by email are fine by me, not sure about others15:29
stubI tend to think email would be a better forum rather than playing Chinese whispers.15:30
matsubarayeah15:30
matsubara[action] matsubara to talk to TL about not having the LP production meeting anymore or change its format15:32
MootBotACTION received:  matsubara to talk to TL about not having the LP production meeting anymore or change its format15:32
matsubaraand for the next one, let's try to have it at 16UTC. I'll email the QA contacts to let everyone know.15:32
matsubara[action] matsubara to email Qa contacts about next LP prod. meeting at 16UTC15:33
MootBotACTION received:  matsubara to email Qa contacts about next LP prod. meeting at 16UTC15:33
stubAt that hour, it will be drunk from a gogo bar :)15:33
matsubara[action] matsubara to email losas about their weekly report15:33
MootBotACTION received:  matsubara to email losas about their weekly report15:33
matsubarahehe15:33
matsubaraand I think that's all for today15:33
matsubaraThank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.15:33
noodles775Thanks matsubara15:34
matsubara#endmeeting15:34
MootBotMeeting finished at 09:34.15:34
=== matsubara is now known as matsubara-lunch
=== salgado-lunch is now known as salgado
=== matsubara-lunch is now known as matsubara
=== bigjools-afk is now known as bigjools
=== salgado is now known as salgado-afk
=== EdwinGrubbs is now known as Edwin-lunch
=== matsubara is now known as matsubara-afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!