Skip to content
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

Should I retry if get error "hinted handoff queue not empty"? #571

Open
hongbo-miao opened this issue Apr 4, 2023 · 0 comments
Open

Should I retry if get error "hinted handoff queue not empty"? #571

hongbo-miao opened this issue Apr 4, 2023 · 0 comments

Comments

@hongbo-miao
Copy link

hongbo-miao commented Apr 4, 2023

We are using InfluxDB Enterprise, I can understand how hinted handoff queue works.

And if we see this error "hinted handoff queue not empty" in the data node log, it is fine.

Because based on this

This error is informational only and does not necessarily indicate a problem in the cluster. It indicates that the node handling the write request currently has data in its local hinted handoff queue for the destination node. Coordinating nodes will not attempt direct writes to other nodes until the hinted handoff queue for the destination node has fully drained.

So the data is still in current data node, and just won't sync to the other node until the hinted handoff queue in the other node clear, it will try later.

Here is my question, we are using this influxdb-client-python to write data. I am wondering if we get the same error from this Python client which returns from data node. In this case, it means the data has not been written to InfluxDB successfully and need retry, right? Thanks!

(500)
Reason: Internal Server Error
HTTP response headers: ...
HTTP response body: b'{"error":"write failed: hinted handoff queue not empty"}\n'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant