Any idea what can cause this? Can it be misconfiguration? Could it be
because I'm messing with MySQL's memory usage so much, or the thread
My config is linked at the bottom, for reference. I might be doing
something terribly dumb.
The stuff I've done under "# * Fine Tuning" worries me the most, but I'm
just not sure how I might be causing this.
I've seen things like this on other servers before but never been able to
nail down the issue. So my config options being the common denominator here
- I suspect that it's something I'm doing.
However - if there were missing commits, the data is gone as you said - so
wouldn't I never see it to begin with?
On Tue, Feb 26, 2013 at 4:29 PM, Reindl Harald <h.reindl@stripped>wrote:
> Am 26.02.2013 22:16, schrieb Zachary Stern:
> > It's InnoDB but it's not just about the number of rows.
> > The data literally isn't there. It's like rows at the end are being
> > dropped. We have a frontend that queries and shows the data, but it ends
> > missing results.
> > I've asked the devs to review the code to see if their could be
> > anywhere, but according to them, there's nothing
> smells like transactions with missing commits
> the thread which started the transaction and inserted data
> will see the data, only this thread, and without a commit
> after close the connection the data are gone because this
> is how transactions are supposed to work -> ACID
zachary alex stern I systems architect
o: 212.363.1654 x106 | f: 212.202.6488 | zs@stripped
60-62 e. 11th street, 4th floor | new york, ny | 10003