| opendevreview | Amit Uniyal proposed openstack/nova stable/wallaby: fup: Print message logging uncaught nova-manage exceptions https://review.opendev.org/c/openstack/nova/+/877334 | 05:18 |
|---|---|---|
| Uggla | gibi, Hi I agree that currently nothing prevent leaking the share if you delete the VM. | 08:45 |
| bauzas | Uggla: you tested it ? | 08:47 |
| bauzas | that was my question | 08:48 |
| Uggla | yes | 08:48 |
| bauzas | ok, so | 08:49 |
| bauzas | https://review.opendev.org/c/openstack/nova/+/831193/24/nova/db/main/models.py#677 | 08:49 |
| bauzas | that means the FK would be not relationed | 08:50 |
| Uggla | gibi, I'm surprised regarding the mount error not tracked, any idea about what is causing the issue. Firewalling maybe ? | 08:51 |
| gibi | Uggla: what manila config you used for testing? I tried the default that is DHSS=True + GenericDriver | 08:53 |
| Uggla | gibi, DHSS=false LVM driver | 08:55 |
| gibi | Uggla: is there a reason why GenericDriver + DHSS=true would not work? | 08:55 |
| gibi | (I'm restacking with LVM DSSF=false now) | 08:55 |
| gibi | *DHSS | 08:56 |
| Uggla | gibi, to be honest I have not tested with DHSS=false thinking that in our context that was not necessary. So I don't know. :( | 08:57 |
| bauzas | so, IMHO, we should delete the share mapping in the instance delete call | 08:58 |
| bauzas | as we can't use the delete cascade SQL support | 08:58 |
| Uggla | bauzas, yep and add the semaphore to avoid any race. | 08:58 |
| bauzas | + in init_instance(), recreating the share like I said | 08:59 |
| bauzas | and maybe a periodic for making sure we don't leak any shares | 08:59 |
| bauzas | Uggla: can you look at what happens to the foreign key ? | 09:00 |
| Uggla | bauzas, yes I'll try to simulate it again. | 09:01 |
| bauzas | cool | 09:03 |
| opendevreview | Hiroki Narukawa proposed openstack/nova master: libvirt: retry libvirt connection on live_migration_monitor https://review.opendev.org/c/openstack/nova/+/867077 | 10:57 |
| opendevreview | Rajesh Tailor proposed openstack/nova master: Fix duplicate cell creation with same name https://review.opendev.org/c/openstack/nova/+/876940 | 13:35 |
| bauzas | gibi: sean-k-mooney: other cores, we need this https://review.opendev.org/c/openstack/nova-specs/+/876887 to be merged quick soon please | 14:17 |
| bauzas | quite* soon | 14:17 |
| sean-k-mooney | ah the redirects sure ill look now | 14:21 |
| gibi | good for me | 14:21 |
| sean-k-mooney | same looks fine | 14:22 |
| sean-k-mooney | im happy the script worked with the new name format | 14:22 |
| opendevreview | Merged openstack/nova-specs master: Move Antelope implemented specs https://review.opendev.org/c/openstack/nova-specs/+/876887 | 14:30 |
| opendevreview | Maxim Monin proposed openstack/nova master: Server Rescue leads to Server ERROR state if base image is deleted https://review.opendev.org/c/openstack/nova/+/872385 | 14:36 |
| bauzas | thanks folks | 14:38 |
| gibi | bauzas: I'm happy that you are only asking me to review these realtively easy patches as otherwise I would have to say no :) | 15:17 |
| bauzas | #startmeeting nova | 16:00 |
| opendevmeet | Meeting started Tue Mar 14 16:00:06 2023 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| opendevmeet | The meeting name has been set to 'nova' | 16:00 |
| bauzas | howdy folks | 16:00 |
| dansmith | o/ | 16:00 |
| bauzas | #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | 16:00 |
| bauzas | ok, let's start, people can join meanwhile | 16:01 |
| gibi | o/ | 16:01 |
| bauzas | #topic Bugs (stuck/critical) | 16:01 |
| bauzas | #info No Critical bug | 16:01 |
| bauzas | #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16 new untriaged bugs (+2 since the last meeting) | 16:01 |
| elodilles | o/ | 16:01 |
| auniyal | o/ | 16:01 |
| bauzas | elodilles: I saw you did a bit of triage | 16:02 |
| elodilles | yepp | 16:02 |
| bauzas | I also looked at the new bugs todayt | 16:02 |
| elodilles | thanks! | 16:02 |
| bauzas | (to see whether we were regressing) | 16:02 |
| bauzas | elodilles: nothing you want to discuss ? | 16:02 |
| auniyal | bauzas, regarding this - https://bugs.launchpad.net/nova/+bug/2011567 | 16:02 |
| auniyal | The message right now is, "fill this in after the PTG", shall we update it to something else. | 16:02 |
| gmann | o/ | 16:02 |
| bauzas | auniyal: as I said as a comment, we don't have cycle priorities | 16:03 |
| bauzas | so, either we delete the Bobcat file, or meh | 16:03 |
| sean-k-mooney | we have kept it for other release | 16:04 |
| sean-k-mooney | its been blank for years at this point | 16:04 |
| bauzas | yup, that's what I wrote | 16:04 |
| bauzas | we can provide some upstream priorities if we want | 16:04 |
| auniyal | okay, the msg seems like we missed to update after PTG | 16:04 |
| bauzas | but, if we don't have anyone, should we delete the file ? | 16:04 |
| sean-k-mooney | im ok either way | 16:05 |
| bauzas | we could discuss this in the PTG if we want | 16:05 |
| sean-k-mooney | sure | 16:05 |
| bauzas | kk | 16:05 |
| auniyal | ack | 16:05 |
| bauzas | let's do this then | 16:05 |
| bauzas | auniyal: I also closed your other bug report https://bugs.launchpad.net/nova/+bug/2011564 | 16:05 |
| bauzas | auniyal: as I said, those links are just examples | 16:05 |
| auniyal | yes, that I missed the example | 16:05 |
| auniyal | my bad | 16:06 |
| bauzas | ok | 16:06 |
| bauzas | moving on then | 16:06 |
| elodilles | about your question bauzas : there was a serialproxy TR. serialproxy example client seems very old and not really functional (bug: https://bugs.launchpad.net/nova/+bug/2009956 ) | 16:06 |
| elodilles | i guess low prio is OK for that | 16:07 |
| elodilles | but correct me if i was wrong | 16:07 |
| bauzas | elodilles: mmm, good question | 16:07 |
| bauzas | 'low' is good for me | 16:07 |
| sean-k-mooney | we expect the serial proxy to be used with netcat in generalright | 16:07 |
| sean-k-mooney | oh actully we expeort it as a websocket | 16:08 |
| sean-k-mooney | so you need a websocket client | 16:08 |
| bauzas | sean-k-mooney: netcat or any script like https://docs.openstack.org/nova/latest/contributor/testing/serial-console.html | 16:09 |
| elodilles | yes, rather a websocket client | 16:09 |
| sean-k-mooney | ya so i dont really consider the example in the docs to be maintained | 16:09 |
| sean-k-mooney | if its not tested its broken by default | 16:09 |
| sean-k-mooney | and we dont test that | 16:09 |
| elodilles | ack | 16:09 |
| bauzas | well, then should we deprecate this API ? | 16:10 |
| sean-k-mooney | so we proably shoudl fix this and by either providing a new nova console script that we test or delete the current example and document using a diffent client | 16:10 |
| bauzas | as a signal | 16:10 |
| sean-k-mooney | no | 16:10 |
| sean-k-mooney | it works fine in horizon | 16:10 |
| bauzas | saying "sorry, we don't really test it" | 16:10 |
| sean-k-mooney | or it did the last time i used it | 16:10 |
| sean-k-mooney | we shoudl remove the example script | 16:10 |
| bauzas | sean-k-mooney: looks to me elodilles tested this with master and it wasn't longer working | 16:11 |
| sean-k-mooney | elodilles: did you test it with horizon | 16:11 |
| sean-k-mooney | or that test script | 16:11 |
| bauzas | I can try to test it with https://github.com/vi/websocat | 16:11 |
| elodilles | sean-k-mooney: well, I don't know whether my devstack was properly configured, but it didn't work | 16:11 |
| elodilles | neither with any old clients | 16:12 |
| elodilles | so i don't know whether this is a problem in serial proxy or the clients | 16:12 |
| sean-k-mooney | ack we shoudl look into this more i dont currently have a devstack but i can try and find time to deploy one and see | 16:12 |
| sean-k-mooney | elodilles: if you can try configuring horizon to use it that would be the main way its used | 16:13 |
| bauzas | me too | 16:13 |
| elodilles | sean-k-mooney: ack | 16:13 |
| bauzas | maybe let's put the importance to Medium, as this is an API | 16:13 |
| sean-k-mooney | https://docs.openstack.org/nova/xena/admin/remote-console-access.html#serial | 16:13 |
| sean-k-mooney | its not an api | 16:14 |
| sean-k-mooney | but it is a fully supprot compenet | 16:14 |
| bauzas | ah yes | 16:14 |
| bauzas | you're right | 16:14 |
| bauzas | a specific service | 16:14 |
| sean-k-mooney | yep | 16:15 |
| bauzas | with another port | 16:15 |
| sean-k-mooney | its just an alternivte to the novnc proxy | 16:15 |
| elodilles | anyway, i've changed its prio to Medium | 16:15 |
| bauzas | anyway, let's not try to find the solution here | 16:15 |
| elodilles | ++ | 16:15 |
| bauzas | elodilles: if you want, I can help you, ping me tomorrow | 16:15 |
| bauzas | I don't think this is an Antelope regression btw. | 16:16 |
| elodilles | bauzas: ack, thanks | 16:16 |
| bauzas | moving on | 16:16 |
| bauzas | #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster | 16:16 |
| bauzas | #info bug baton is being passed to auniyal | 16:17 |
| bauzas | auniyal: you're ok with that ? | 16:17 |
| auniyal | yes, | 16:17 |
| bauzas | cool | 16:18 |
| bauzas | #topic Gate status | 16:18 |
| bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | 16:18 |
| bauzas | #link https://etherpad.opendev.org/p/nova-ci-failures | 16:18 |
| bauzas | I'll be honest, I haven't uploaded a lot of implementation changes this week | 16:18 |
| bauzas | so I had not found any problem | 16:19 |
| bauzas | so looks to me the gate is now better :) | 16:19 |
| elodilles | :] | 16:19 |
| dansmith | yeah, lots of small changes have improved things a lot | 16:19 |
| bauzas | but we'll see after a few time, when we're back | 16:19 |
| bauzas | for the moment, the gate doesn't run a lot of jobs | 16:19 |
| bauzas | job runs* I mean | 16:20 |
| bauzas | and in general, we know the gate becomes bad around the milestones | 16:20 |
| bauzas | so we'll see how it goes later | 16:20 |
| bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status | 16:20 |
| bauzas | all greens here | 16:20 |
| bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | 16:20 |
| bauzas | #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures | 16:21 |
| bauzas | #topic Release Planning | 16:21 |
| bauzas | #link https://releases.openstack.org/antelope/schedule.html | 16:21 |
| bauzas | #info This week is the last time for creating a new RC if we need it. | 16:21 |
| bauzas | #link https://etherpad.opendev.org/p/nova-antelope-rc-potential | 16:21 |
| bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=antelope-rc-potential no open regression bugs were found. | 16:21 |
| bauzas | so, yeah I looked at the open bugs and I haven't found any regression | 16:21 |
| bauzas | I also tried to look at the 'In Progress' bugs | 16:22 |
| bauzas | https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=In%20Progress&orderby=-datecreated&start=0 | 16:22 |
| bauzas | by Age | 16:22 |
| bauzas | amirite by saying none of the 8 in-progress bug reports we have since 2 months are not regressions ? I hope so | 16:24 |
| bauzas | anyway, will continue to look at those bugs | 16:25 |
| bauzas | because as I said, this is the last week for a new release candidate | 16:25 |
| bauzas | #link https://releases.openstack.org/bobcat/schedule.html | 16:26 |
| gibi | would be nice to have a release where we dont need RC2 | 16:26 |
| bauzas | you'll be interested in the below : | 16:26 |
| bauzas | #link https://review.opendev.org/c/openstack/releases/+/877094 Proposed deadlines for Bobcat | 16:26 |
| bauzas | we'll discuss those proposal dates at the PTG | 16:27 |
| bauzas | vPTG I mean | 16:27 |
| bauzas | but you can start to write comments if you wish | 16:27 |
| bauzas | moving on I guess | 16:28 |
| bauzas | oh | 16:28 |
| bauzas | I was about to forge | 16:28 |
| bauzas | forget | 16:28 |
| bauzas | I created all bobcat launchpad series for placement, novaclient and nova | 16:29 |
| bauzas | now, we said to try to remove placement from storyboard | 16:29 |
| bauzas | so I started to look and it looks difficult | 16:30 |
| bauzas | #info as a reminder, please no longer use Storyboard for creating feature requests or bug reports https://storyboard.openstack.org/#!/project/list?q=placement | 16:30 |
| bauzas | but I'll try to see if I can do anything with https://opendev.org/ttygroup/boartty/ | 16:30 |
| bauzas | moving on | 16:31 |
| bauzas | #topic vPTG Planning | 16:31 |
| bauzas | usual reminder | 16:32 |
| bauzas | #link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-483971570997 Register your free ticket | 16:32 |
| bauzas | #link https://etherpad.opendev.org/p/nova-bobcat-ptg PTG etherpad | 16:32 |
| bauzas | now this is time | 16:32 |
| bauzas | #info please add your topics before end of this week, so I could provide an agenda on Monday. | 16:32 |
| bauzas | this is important | 16:32 |
| bauzas | as I don't see a lot of topics yet in the ptg etherpad | 16:32 |
| bauzas | (well, I actually wrote the majority of them) | 16:33 |
| bauzas | also, if you want to discuss with other teams, please add your topics in the cross-project agenda | 16:33 |
| bauzas | and then I'll ping the other PTLs in order to find some time | 16:33 |
| bauzas | as a reminder, I asked for 4 days of 4 hours | 16:34 |
| bauzas | but if the agenda remains quite empty as it is, I'll probably unbook the Friday rooms | 16:34 |
| sean-k-mooney | if it was in person i would suggest using the firday slot for an unconfernce/hackaton | 16:35 |
| sean-k-mooney | but i kind of hate the idea of doing that virutally | 16:35 |
| bauzas | don't get me on that direction :) | 16:35 |
| sean-k-mooney | so sure | 16:35 |
| sean-k-mooney | we could keep the slot and decied durign the ptg | 16:36 |
| bauzas | I mean, after 3 vPTGs, I'm quite done with them | 16:36 |
| sean-k-mooney | i.e. if there is a topic we ant to come back too | 16:36 |
| bauzas | surely | 16:36 |
| bauzas | and I'm pretty sure people will add topics on the last time like every cycle.. | 16:36 |
| bauzas | (tbc, I'm also doing this game) | 16:36 |
| bauzas | but even with that, I just feel Friday will be either off or hackathon | 16:37 |
| bauzas | fwiw, my main priorities for the beginning of Bobcat is to review some series we accepted | 16:37 |
| bauzas | like the manila one, which I'll probably help too | 16:37 |
| sean-k-mooney | if we have noting to do on firday im fine with just say "thanks for coming folks" and doing a spec review day or something | 16:38 |
| bauzas | sure | 16:38 |
| bauzas | that's an idea | 16:38 |
| bauzas | anyway | 16:38 |
| bauzas | fwiw, the ptg main agenda is at the moment not large https://ptg.opendev.org/ptg.html | 16:39 |
| bauzas | hopefully projects will book their rooms next week | 16:39 |
| bauzas | (one thing I also think we miss with *virtual* PTGs is those kind of cross-project large discussions we had before) | 16:40 |
| bauzas | but meh, moving on | 16:40 |
| bauzas | #topic Review priorities | 16:41 |
| bauzas | #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2) | 16:41 |
| bauzas | #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review | 16:41 |
| bauzas | #topic Stable Branches | 16:41 |
| bauzas | elodilles: your time | 16:41 |
| elodilles | well, nothing special | 16:41 |
| elodilles | i mean, not so many patches merge | 16:41 |
| elodilles | but as far as i see: | 16:41 |
| elodilles | #info stable gates seem to be OK - though it's hard to merge patches due to intermittent failures | 16:42 |
| elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | 16:42 |
| elodilles | that's all :X | 16:42 |
| bauzas | elodilles: dansmith: afaik, we haven't backported the mysqld memory reduction changes into stable branches ? | 16:43 |
| dansmith | a bunch of the things we've fixed haven't been backported to stable, | 16:43 |
| dansmith | so I expect that will remain challenging | 16:43 |
| bauzas | hah, jinx | 16:43 |
| bauzas | we could work on that | 16:43 |
| dansmith | I haven't been monitoring the mysql memory thing, but it seems like that _has_ helped yeah/ | 16:43 |
| opendevreview | Alexey Stupnikov proposed openstack/nova master: Don't remove cached base images for failed resize ops https://review.opendev.org/c/openstack/nova/+/877410 | 16:44 |
| dansmith | there was a potential for negative impacts, but I've heard no complaints | 16:44 |
| elodilles | dansmith: do you have a topic set for those patches? so that I could see whether some could be backported? | 16:45 |
| bauzas | mmmh | 16:45 |
| dansmith | elodilles: this in devstack plus the flag enabled: https://review.opendev.org/c/openstack/devstack/+/873646 | 16:45 |
| elodilles | dansmith: thanks, i'll have a look | 16:46 |
| bauzas | example here https://review.opendev.org/c/openstack/nova/+/874664 | 16:46 |
| bauzas | dansmith: but that means we would need to backport the devstack change too right? | 16:47 |
| dansmith | that's why I said "this in devstack" | 16:47 |
| dansmith | meaning you need it in the devstack branc you're running on | 16:47 |
| elodilles | the nova patch is at least part of stable/2023.1 :) | 16:47 |
| dansmith | which is kinda :/ | 16:47 |
| sean-k-mooney | so the memory patch proably shoudl be backported in devstack | 16:48 |
| bauzas | yeah | 16:48 |
| sean-k-mooney | becuase i think that might be useful on other stable branches | 16:48 |
| bauzas | https://review.opendev.org/c/openstack/devstack/+/873646/3/lib/databases/mysql I understand dansmith's concerns | 16:48 |
| bauzas | but it looks to me mysql doesn't bubble up the memory | 16:48 |
| dansmith | I don't have specific concerns | 16:48 |
| dansmith | if it's really that impactful, it's probably worth it, | 16:49 |
| bauzas | do we have some mysql monitoring in devstack ? | 16:49 |
| dansmith | it's just that it takes the devstack patch on each branch, plus job changes to enable | 16:49 |
| dansmith | bauzas: we have my performance.json which has the info in it | 16:49 |
| dansmith | gmann specifically didn't want to enable by default until bobcat (understandable) | 16:49 |
| dansmith | so backporting to stable is kinda the opposite of that :) | 16:50 |
| bauzas | yeah, I can understand | 16:50 |
| bauzas | we shouldn't default this to all the jovs | 16:50 |
| bauzas | obs | 16:50 |
| bauzas | damn, jobs even | 16:50 |
| sean-k-mooney | why not | 16:50 |
| dansmith | the concerns are that it could slow down mysql and introduce other performance regressions that manifest as failures | 16:50 |
| dansmith | it hasn't seemed to have done that in practice, | 16:50 |
| sean-k-mooney | did we see a change in the job execution time | 16:50 |
| sean-k-mooney | right | 16:50 |
| dansmith | but the thought was to minimize the risk, in an already risky environment | 16:51 |
| bauzas | sean-k-mooney: because of the fact we don't really monitor mysqld runs | 16:51 |
| bauzas | in the logs | 16:51 |
| dansmith | bauzas: what does that mean? | 16:51 |
| sean-k-mooney | and reducing memory pressure might actully reduce swapping and speed up the job | 16:51 |
| dansmith | bauzas: I think we do monitor it plenty, it's just that it's a pretty core function and breaking it could have lots and lots of wide impacts, both obvious and non-obvious | 16:51 |
| bauzas | dansmith: correct me if I'm wrong, but do we trace the mysql performance in the logs, you said we have that in performance.yaml | 16:51 |
| bauzas | I should take a look at this file | 16:52 |
| bauzas | (tbh) | 16:52 |
| dansmith | performance.json | 16:52 |
| dansmith | there's a lot of data in there, but memory is probably the only relevant bit | 16:52 |
| sean-k-mooney | we dont messure query reponce time as far as i know but we moditor memory usage | 16:52 |
| dansmith | I'm just saying I don't know what "monitor mysqld runs" means in this context | 16:52 |
| dansmith | yeah, no query time logging, but that would need to be done in aggregate to have any sort of meaningful result I think | 16:53 |
| sean-k-mooney | as long as we are not seeing errors form teh services (timeouts) or longer overall job runs that all we really need to know | 16:53 |
| dansmith | *and* it's time-based which is nearly impossible to compare across runs in the gate | 16:53 |
| dansmith | sean-k-mooney: right, well, not having it on by default in master yet, we don't really have that large of a sample | 16:54 |
| dansmith | we have a few jobs that are already atypical opt-ed into it | 16:54 |
| bauzas | dansmith: I'll look at what we get from performance.yaml | 16:54 |
| dansmith | anyway, I was good to go default on, but there's definitely risk so we just have to keep that in mind | 16:54 |
| dansmith | bauzas: please stop saying performance.yaml :) | 16:54 |
| dansmith | it's performance.json dammit :D | 16:54 |
| bauzas | my question was more about the fact that given we have less large temporary tables and innodb pool sizes, I'd love to see some mysql insights about botyh | 16:55 |
| bauzas | oh f, you're right | 16:55 |
| bauzas | pardon my YAML | 16:55 |
| sean-k-mooney | ... | 16:55 |
| bauzas | anyway, we're quite at the end of the meeting | 16:55 |
| bauzas | #topic Open discussion | 16:55 |
| bauzas | the agenda is free from any item | 16:56 |
| bauzas | so, anything to say ? | 16:56 |
| bauzas | looks not | 16:57 |
| bauzas | thanks all | 16:57 |
| bauzas | #endmeeting | 16:57 |
| opendevmeet | Meeting ended Tue Mar 14 16:57:34 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:57 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2023/nova.2023-03-14-16.00.html | 16:57 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-03-14-16.00.txt | 16:57 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2023/nova.2023-03-14-16.00.log.html | 16:57 |
| sean-k-mooney | bauzas: for what its worth i remember turnign mysql for low memory foot print many years ago when i first started workign on openstack | 16:59 |
| sean-k-mooney | there used to be a blog or doc that told you how to do it | 16:59 |
| sean-k-mooney | i dont know where that was cause its been years but this type of change is not new to me | 16:59 |
| bauzas | sean-k-mooney: AFAIR, you can use mysql's information schema tables to get the recommended pool sizes | 17:00 |
| bauzas | but I was a mysql operator a decade ago and my brain is fried now | 17:00 |
| sean-k-mooney | probably but i dont really have concern with the value that are bing used | 17:00 |
| sean-k-mooney | i think we used to do this in the intel nfv ci | 17:00 |
| sean-k-mooney | to reduce memoryusage because we were deploying with ovs-dpdk | 17:01 |
| bauzas | for the temp tables, well that's less of a concern | 17:01 |
| bauzas | iirc, if the tmp tables aren't large enough, this just goes on disk | 17:01 |
| sean-k-mooney | no it was for the pools as well | 17:01 |
| bauzas | so this becomes an I/O performance question | 17:02 |
| sean-k-mooney | right i dont think it will be in our usage | 17:02 |
| sean-k-mooney | we will see but i would prefer to see by turning this on by default in all the jobs | 17:02 |
| sean-k-mooney | and seeign if we see any regressions | 17:02 |
| bauzas | so, I double-checked and yeah the pools are for caching | 17:03 |
| sean-k-mooney | yep | 17:03 |
| bauzas | so in case the pools aren't large enough, this is just a disk io performance concern as well | 17:03 |
| sean-k-mooney | both of result sets and quey execution plans i belive | 17:03 |
| sean-k-mooney | bauzas: yep but we are already swappign to disk in several jobs | 17:04 |
| sean-k-mooney | if we can reduce that it likely will improve perfromce over all | 17:04 |
| bauzas | yeah, now I refresh my mind | 17:04 |
| sean-k-mooney | basically what im saying is any perfromance hit form the mysql turning will likely be offset by reduced memory pressure over all | 17:05 |
| bauzas | I remember we can call the innodb engine to get the performance metrics | 17:05 |
| auniyal | this :( https://zuul.openstack.org/status#864055, its always fail on gate | 18:11 |
| * gibi gibi_pto | 18:37 | |
| *** gibi is now known as gibi_pto | 18:38 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!