influxdata / influxdata/influxdb-client-python

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

Open
#571 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
793
Forks
186
Avg merge
3h 2m
Merged PRs (30d)
1

Description

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'

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Python client's write path and its handling of the HTTP 500 response body shown in the issue, then compare that behavior with the linked InfluxDB Enterprise hinted-handoff guidance. Done means clearly documenting whether this response indicates unsuccessful writing and whether callers should retry.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.