Troubleshoot issues writing data
InfluxDB Clustered is currently only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.
Learn how to avoid unexpected results and recover from errors when writing to InfluxDB Clustered.
Handle write responses
In InfluxDB Clustered, writes are synchronous.
After InfluxDB validates the request and ingests the data, it sends a success response (HTTP
204 status code) as an acknowledgement that the data is written and queryable.
To ensure that InfluxDB handles writes in the order you request them, wait for the acknowledgement before you send the next request.
If InfluxDB successfully writes all the request data to the database, it returns success (HTTP
204 status code).
The first rejected point in a batch causes InfluxDB to reject the entire batch and respond with an HTTP error status.
Review HTTP status codes
InfluxDB uses conventional HTTP status codes to indicate the success or failure of a request.
message property of the response body may contain additional details about the error.
Write requests return the following status codes:
|HTTP response code
|If InfluxDB ingested the data
400 "Bad request"
message contains the first malformed line
|If data is malformed
Authorization header is missing or malformed or if the token doesn’t have permission to write to the database. See examples using credentials in write requests.
404 "Not found"
|requested resource type (for example, “organization” or “database”), and resource name
|If a requested resource (for example, organization or database) wasn’t found
500 "Internal server error"
|Default status for an error
503 “Service unavailable”
|If the server is temporarily unavailable to accept writes. The
Retry-After header describes when to try the write again.
If your data did not write to the database, see how to troubleshoot rejected points.
If you notice data is missing in your database, do the following:
- Check the
messageproperty in the response body for details about the error.
- If the
messagedescribes a field error, troubleshoot rejected points.
- Verify all lines contain valid syntax (line protocol).
- Verify the timestamps in your data match the precision parameter in your request.
- Minimize payload size and network errors by optimizing writes.
Troubleshoot rejected points
InfluxDB rejects points that fall within the same partition (default partitioning is measurement and day) as existing bucket data and have a different data type for an existing field.
Check for field data type differences between the rejected data point and points within the same database and partition–for example, did you attempt to write
string data to an
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.