You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing batches of points to Influx (via the InfluxDB::batchOf mechanism) over UDP it is easy to accidentally exceed the maximum UDP packet size. This causes an exception to be raised in UDP::send which ultimately results in the loss of the entire batch of points.
I propose that InfluxDB::flushBatch should be aware of the largest message that can be transmitted over its Transport and sends the Points in the largest batch possible.
The text was updated successfully, but these errors were encountered:
When writing batches of points to Influx (via the
InfluxDB::batchOf
mechanism) over UDP it is easy to accidentally exceed the maximum UDP packet size. This causes an exception to be raised inUDP::send
which ultimately results in the loss of the entire batch of points.I propose that
InfluxDB::flushBatch
should be aware of the largest message that can be transmitted over itsTransport
and sends the Points in the largest batch possible.The text was updated successfully, but these errors were encountered: