-
-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increased bulk insert size to avoid partial inserts and potential data loss. #4808
Comments
Yea, I say crap! Can you bump the number in |
You mean the 1000 here: Line 391 in 1235955
to 2000? |
Yup. I hate to do it this way, this is a complicated problem, and I'm trying to have a simplified summer from a personal perspective. Work is pretty complicated, but only occupies 8 hours a day 👍 |
O.K. Set it to 2000 as temporary workaround. poller_output table is now empty again and I haven't received any notification emails since then either. |
- WARNING: Poller Output Table not Empty - This is a summer solution. The real solution is a bit more complicated
I've increased the insert size for |
Describe the bug
I have just upgraded from 1.2.15 to 1.2.21 on CentOS 7 using the EPEL 7 RPM.
I now see this error for two data sources of two different devices on every poller run every 5 minute.s
If I delete the graph & data source and recreate it, the error just moves to the next following data source id on the same device.
The problem looks very much like issue #4687 but I still have the issue with 1.2.21.
I run the command suggested in #4687 and it showed something interesting:
It looks the same on the other device:
So it seems that exactly for the data source id during which the
Writing 1001 items to Poller Output Table
happens it won't clear out the poller output table correctly.I have two other devices which very many data sources. However, when I run the command on those two it looks like this:
Here, the "Writing 1001 items to Poller Output Table" happens exactly between the data sources and not in the middle of it.
The text was updated successfully, but these errors were encountered: