So that definitely got lost in translation somewhere, and is about to have us spam icehouse users with messages that make them think their openstack cluster is going to burn to the ground. Is there proposed reviews to set those defaults in projects up already?
Remember - WARN is a level seen by administrators, and telling everyone
they have silent data corruption is not a good default.
-Sean
On 03/03/2014 02:05 PM, Roman Podoliaka wrote:
> Hi all,
>
> This is just one another example of MySQL not having production ready
> defaults. The original idea was to force setting the SQL mode to
> TRADITIONAL in code in projects using oslo.db code when "they are ready"
> (unit and functional tests pass). So the warning was actually for
> developers rather than for users.
>
> Sync of the latest oslo.db code will make users able to set any SQL mode
> you like (default is TRADITIONAL now, so the warning is gone).
>
> Thanks,
> Roman
>
> On Mar 2, 2014 8:36 PM, "John Griffith" <john.griff...@solidfire.com
> <mailto:john.griff...@solidfire.com>> wrote:
>>
>>
>>
>>
>> On Sun, Mar 2, 2014 at 7:42 PM, Sean Dague <s...@dague.net
> <mailto:s...@dague.net>> wrote:
>>>
>>> Coming in at slightly less than 1 million log lines in the last 7 days:
>>>
> http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVGhpcyBhcHBsaWNhdGlvbiBoYXMgbm90IGVuYWJsZWQgTXlTUUwgdHJhZGl0aW9uYWwgbW9kZSwgd2hpY2ggbWVhbnMgc2lsZW50IGRhdGEgY29ycnVwdGlvbiBtYXkgb2NjdXJcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5MzgxNDExMzcyOX0=
>>>
>>> "This application has not enabled MySQL traditional mode, which means
>>> silent data corruption may occur"
>>>
>>> This is being generated by *.openstack.common.db.sqlalchemy.session in
>>> at least nova, glance, neutron, heat, ironic, and savana
>>>
>>>
> http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVGhpcyBhcHBsaWNhdGlvbiBoYXMgbm90IGVuYWJsZWQgTXlTUUwgdHJhZGl0aW9uYWwgbW9kZSwgd2hpY2ggbWVhbnMgc2lsZW50IGRhdGEgY29ycnVwdGlvbiBtYXkgb2NjdXJcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5MzgxNDExMzcyOSwibW9kZSI6InNjb3JlIiwiYW5hbHl6ZV9maWVsZCI6Im1vZHVsZSJ9
>>>
>>>
>>> At any rate, it would be good if someone that understood the details
>>> here could weigh in about whether is this really a true WARNING that
>>> needs to be fixed or if it's not, and just needs to be silenced.
>>>
>>> -Sean
>>>
>>> --
>>> Sean Dague
>>> Samsung Research America
>>> s...@dague.net <mailto:s...@dague.net> / sean.da...@samsung.com
> <mailto:sean.da...@samsung.com>
>>> http://dague.net
>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
> <mailto:OpenStack-dev@lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> I came across this earlier this week when I was looking at this in
> Cinder, haven't completely gone into detail here, but maybe Florian or
> Doug have some insight?
>>
>> https://bugs.launchpad.net/oslo/+bug/1271706
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
> <mailto:OpenStack-dev@lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Sean Dague
Samsung Research America
s...@dague.net / sean.da...@samsung.com
http://dague.net
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
