influxdata / influxdata/influxdb

Data loss after converting TSM to TSI

Open
#20,189 0 comments 0 reactions 0 assignees View on GitHub
1.x
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

ISSUE : Data loss after converting TSM to TSI Indexing .

VERSION : 1.8.0

HOW TO REPRODUCE :
1) Large amount of data should exist in TSM index format.
2) Convert TSM to TSI by below command:
![image](https://user-images.githubusercontent.com/63041681/100442300-c404a600-30cd-11eb-8e03-99c1ddc2a3da.png)
3) Make sure permission are correct:
![image](https://user-images.githubusercontent.com/63041681/100442371-e4ccfb80-30cd-11eb-94cc-98ddcfb57db8.png)
4)Restart influxdb
![image](https://user-images.githubusercontent.com/63041681/100442396-eeeefa00-30cd-11eb-8346-a71a3d599fa0.png)

BUG : Every time i try to do this with same set of data , Conversion to TSI is successful but only in 1 measurement past 6 months data is not visible when queried. But shard is present with data .

TEMPORARY FIX : Data is present in shard but can only be queried if i change back to TSM indexing.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the TSM-to-TSI conversion with the same data, permissions, restart, and query sequence described in the issue. Compare query results before and after conversion, and verify that the affected measurement's data remains queryable while the shard is present. Done means the conversion no longer hides the affected data.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.