term solution
> that
> >> >> allows the end-user to still configure this like they were before.
> >> >>
> >> >> I'm currently thinking along the lines of calling something like
> >> >> pool.dispose() in each child immediately aft
pool.dispose() in each child immediately after it is spawned. I think
>> >> this should invalidate all of the existing connections so that when a
>> >> connection is checked out of the pool a new one will be created fresh.
>> >>
>> >> Thoughts? I&#
> >> connection is checked out of the pool a new one will be created fresh.
> >>
> >> Thoughts? I'll be testing. Hopefully, I'll have a fixed patch up soon.
> >>
> >> Cheers,
> >> Carl
> >>
> >> From: Yingjun Li
> &
om: Yingjun Li
>> Reply-To: OpenStack Development Mailing List
>>
>> Date: Thursday, September 5, 2013 8:28 PM
>> To: OpenStack Development Mailing List
>>
>> Subject: Re: [openstack-dev] [Neutron] The three API server multi-worker
>> process pa
Yingjun Li
> Reply-To: OpenStack Development Mailing List
>
> Date: Thursday, September 5, 2013 8:28 PM
> To: OpenStack Development Mailing List >
> Subject: Re: [openstack-dev] [Neutron] The three API server multi-worker
> process patches.
>
>
> +1 for Carl's patch
t
Subject: Re: [openstack-dev] [Neutron] The three API server multi-worker
process patches.
+1 for Carl's patch, and i have abandoned my patch..
About the `MySQL server gone away` problem, I fixed it by set
'pool_recycle' to 1 in db/api.py.
在 2013年9月6日星期五，Nachi Ueno
ack Development Mailing List
Date: Thursday, September 5, 2013 8:28 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] The three API server multi-worker
process patches.
+1 for Carl's patch, and i have abandoned my patch..
About the `MySQL server gone away`
+1 for Carl's patch, and i have abandoned my patch..
About the `MySQL server gone away` problem, I fixed it by set
'pool_recycle' to 1 in db/api.py.
在 2013年9月6日星期五，Nachi Ueno 写道：
> Hi Folks
>
> We choose https://review.openstack.org/#/c/37131/ <-- This patch to go on.
> We are also discussing i
Hi Folks
We choose https://review.openstack.org/#/c/37131/ <-- This patch to go on.
We are also discussing in this patch.
Best
Nachi
2013/9/5 Baldwin, Carl (HPCS Neutron) :
> Brian,
>
> As far as I know, no consensus was reached.
>
> A problem was discovered that happens when spawning multiple
Brian,
As far as I know, no consensus was reached.
A problem was discovered that happens when spawning multiple processes.
The mysql connection seems to "go away" after between 10-60 seconds in my
testing causing a seemingly random API call to fail. After that, it is
okay. This must be due to s
Was any consensus on this ever reached? It appears both reviews are still open.
I'm partial to review 37131 as it attacks the problem a more concisely, and, as
mentioned, combined the efforts of the two more effective patches. I would echo
Carl's sentiments that it's an easy review minus the few
11 matches
Mail list logo
