No. read_timeout feature was added to MySQLdb only in 1.2.5. If you're
using Ubuntu, you'll need to update python-sqlalchemy as well or else
the option will be rejected in the MySQL connection string. It could
be backported to 4.0, but there are no repo tools for Ubuntu on Fuel
master node to do an in-place upgrade.

On Wed, Mar 5, 2014 at 10:56 AM, Dmitry Ukov <[email protected]> wrote:
> Thanks for your comments. As far as I can see this change request is
> relevant for Fuel 4.1. But we are using 4.0 release and there is no MySQLdb
> 1.2.5 in this release. Is there any other option to tune those parameters
> without package update?
>
>
> On Tue, Mar 4, 2014 at 9:13 PM, Matthew Mosesohn <[email protected]>
> wrote:
>>
>> Dmitry,
>>
>> Yes. We are very close to release and the patches for RabbitMQ and MySQL
>> reconnection fix this.
>>
>> On Mar 4, 2014 9:02 PM, "Dmitry Ukov" <[email protected]> wrote:
>>>
>>> Hello folks,
>>> I'm observing the following issue with communication between nova-compute
>>> and nova-conductor
>>>  Traceback (most recent call last):
>>>    File
>>> "/usr/lib/python2.6/site-packages/nova/servicegroup/drivers/db.py", line 96,
>>> in _report_state
>>>      service.service_ref, state_catalog)
>>>    File "/usr/lib/python2.6/site-packages/nova/conductor/api.py", line
>>> 269, in service_update
>>>      return self._manager.service_update(context, service, values)
>>>    File "/usr/lib/python2.6/site-packages/nova/conductor/rpcapi.py", line
>>> 397, in service_update
>>>      service=service_p, values=values)
>>>    File "/usr/lib/python2.6/site-packages/nova/rpcclient.py", line 85, in
>>> call
>>>      return self._invoke(self.proxy.call, ctxt, method, **kwargs)
>>>    File "/usr/lib/python2.6/site-packages/nova/rpcclient.py", line 63, in
>>> _invoke
>>>      return cast_or_call(ctxt, msg, **self.kwargs)
>>>    File
>>> "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/proxy.py", line
>>> 130, in call
>>>      exc.info, real_topic, msg.get('method'))
>>>  Timeout: Timeout while waiting on RPC response - topic: "conductor", RPC
>>> method: "service_update" info: "<unknown>"
>>>
>>> After that nova-compute became unavailable nova-conductor and RabbitMQ
>>> services look fine
>>> I'm using Havana release. Any ideas on that issue? Is it possible that
>>> it's connected with VIP migration and rabbit issue?
>>> Thanks in advance.
>>>
>>> --
>>> Kind regards
>>> Dmitry Ukov
>>> IT Engineer
>>> Mirantis, Inc.
>>>
>>>
>>> --
>>> Mailing list: https://launchpad.net/~fuel-dev
>>> Post to     : [email protected]
>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>
>
>
> --
> Kind regards
> Dmitry Ukov
> IT Engineer
> Mirantis, Inc.
>

-- 
Mailing list: https://launchpad.net/~fuel-dev
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~fuel-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to