taosdata / taosdata/TDengine

Cannot add duplicate keys to hash

Open
#34,017 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
25.1k
Forks
5k
Avg merge
4d 59m
Merged PRs (30d)
7

Description

Bug Description

I'm finding a lot of error logs like the one below, and looking at the official docs I'm told to submit an issue, I'd like to know what's causing it and what other information is required from me

12/23 14:30:48.157623 00064205 C TQ  ERROR tmq poll: consumer:0x686734940454a8ab, subkey mdp-sub-omdc-1m-cg:1.omdc_tick, vgId:55, rsp block:0, rsp offset type:wal:102959, QID:0x934007e7365d4097 error msg:Cannot add duplicate keys to hash, line:0
12/23 14:30:48.157643 00064205 C UTL ERROR failed to extract data for mq, msg:Cannot add duplicate keys to hash
12/23 14:30:48.157647 00064205 C DND ERROR vgId:55, msg:0xfffd899a5678, failed to query since Cannot add duplicate keys to hash, QID:0x934007e7365d4097:0x6867349e73611976

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Type in '....'
  3. See error

Expected Behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • Docker Image: tdengine/tsdb:3.3.8.8

Additional Context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

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 reported log sequence and the Docker image tdengine/tsdb:3.3.8.8, then determine a reproducible query or consumer scenario for the "Cannot add duplicate keys to hash" error. The issue is complete when the cause is identified and the reporter has the required reproduction details or a verified fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.