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

Implement influx_inspect tooling #10993

Closed
8 of 9 tasks
e-dard opened this issue Jan 11, 2019 · 2 comments
Closed
8 of 9 tasks

Implement influx_inspect tooling #10993

e-dard opened this issue Jan 11, 2019 · 2 comments
Labels
area/storage area/tooling difficulty/high This issue needs to be broken down into smaller units of work. wontfix

Comments

@e-dard
Copy link
Contributor

e-dard commented Jan 11, 2019

Proposal: [Description of the feature]

We need to convert / port the influx_inspect tools over to 2.0.

Tools that we need to bring over:

  • buildtsi - to rebuild a TSI index;
  • dumptsi - dump low-level details of the TSI index;
  • dumptsm - dump low-level details of tsm1 data;
  • dumptsmwal - dump low-level details of WAL data;
  • reporttsm - report statistics about tsm1 data Port influx_inspect report-tsm tool to 2.0 #10994;
  • reporttsi - report statistics about TSI index data;
  • verifytsm - verify integrity of tsm file;
  • verifyseriesfile - verify integrity of series file.
  • verifywal - verify integrity of WAL.

Current behavior:

We don't have any of the tools ported over from the 1.x line. Due the the architectural changes it's unlikely that many if any of the tools will work without code changes.

Desired behavior:

Tools should be ported with the following semantics:

  • No more databases, retention policies or shards.
  • Data that used to be dumped/reported by database should now be reported by (organisation, bucket).
  • Where possible, filter by organisation and then also bucket.
  • If a tool used to segment/filter on measurement then it now needs to be able to do the same on the _m tag key.

Finally, in 2.0 we have an "all tools in one binary" philosophy, so we need to re-architect the existing tool codebases to provide an exported API that the influx CLI tool can make use of. I would imagine, for example, a use-case like this:

$ influx inspect dump-tsi -measurement-filter "^cpu" ~/.influxdbv2/engine/index

Use case:

We need tooling working on 2.0 so we can debug issues.

@stale
Copy link

stale bot commented Dec 12, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 12, 2019
@stale
Copy link

stale bot commented Dec 19, 2019

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.

@stale stale bot closed this as completed Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/storage area/tooling difficulty/high This issue needs to be broken down into smaller units of work. wontfix
Projects
None yet
Development

No branches or pull requests

1 participant