Hello,
Answears below
---
Best regards
Sławek Kapłoński
sla...@kaplonski.pl
Dnia poniedziałek, 22 września 2014 13:41:51 Jay Pipes pisze:
> Hi Peter, Sławek, answers inline...
>
> On 09/22/2014 08:12 AM, Peter Boros wrote:
> > Hi,
> >
> > StaleDataError is not given by MySQL, but rather SQLAlc
Hi Peter, Sławek, answers inline...
On 09/22/2014 08:12 AM, Peter Boros wrote:
Hi,
StaleDataError is not given by MySQL, but rather SQLAlchemy. After a
quick look, it seems like SQLAlchemy gets this, if the update updated
different number of rows then it expected. I am not sure what is the
expe
Hi,
StaleDataError is not given by MySQL, but rather SQLAlchemy. After a
quick look, it seems like SQLAlchemy gets this, if the update updated
different number of rows then it expected. I am not sure what is the
expectation based on, perhaps soembody can chime in and we can put
this together. What
Hello,
Thanks for Your explanations. I thought so and now I decrease
"idle_connection_timeout" in neutron and nova. Now when master server is back
to cluster than in less than one minute all conections are again made to this
master node becuase old connections which was made to backup node are
Hi,
Let me answer this and one of your previous questions in one because
they are related.
Earlier you wrote:
> I made such modifications today in my infra and generally it looks
> better now. I don't see deadlocks. But I have one more problem with
> that: generally it works fine when main node i
