That's probably just covering up the issue. If we're trying to write to the database it's because there's something important we want to record, and if the write is failing then we're losing some data that we needed to keep. The Logstash query shows that's still happening plenty: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Command%20Out%20of%20Sync%5C%22%20tags:%5C%22screen-h-eng%5C%22
It's nice if we don't completely hose the stack in the process though :) We could consider backporting that patch as a mitigation.
That's probably just covering up the issue. If we're trying to write to the database it's because there's something important we want to record, and if the write is failing then we're losing some data that we needed to keep. The Logstash query shows that's still happening plenty: http:// logstash. openstack. org/#/dashboard /file/logstash. json?query= message: %5C%22Command% 20Out%20of% 20Sync% 5C%22%20tags: %5C%22screen- h-eng%5C% 22
It's nice if we don't completely hose the stack in the process though :) We could consider backporting that patch as a mitigation.