[MCOL-5781] Create columnstore_repair | post dbrm restore or crash - Jira

XML

Word

Printable

Details

Type: New Feature
Status: Open (View Workflow)
Priority: Critical
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
None

Epic Link:
Ease of use

Description

in an effort to create something like mariadb table repair (https://mariadb.com/kb/en/repair-table/) , have a process that steps through the extent map and segment files, identifying inconsistencies between metadata and disk. columnstore_repair would recommend to delete inconsistencies/extents/segments/metadata, to a point where you can at least turn on the database one and query your tables without fear of running into error about missing files, lbids not exiting, hvm out of range, without needing to further clean up the state of the data like running calDropPartitions().

columnstore_repair would deprioritize retaining the most data, but rather prioritizes keeping "good/working" data to get back online faster.

Attachments

Issue Links

is blocked by

MCOL-5945 Reproduce lbids not exiting, hvm out of range Error

Open

relates to

MCOL-313 utility to rebuild column file

Stalled

MCOL-4819 Request for improved recovery options

Closed

MCOL-5584 investigate broken database after kill -9 PrimProc

Open

MCOL-6126 Prevent Data Loss: Local Extent Map Backup on NFS Outages

Open

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(9 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Allen Herrera

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2024-07-17 16:52

Updated:: 6 days ago 17:08

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.