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

Add a boost doctor command to enable SP's to surface known issues #582

Closed
jacobheun opened this issue Jun 9, 2022 · 3 comments
Closed
Labels
area/ux Area: UX kind/enhancement Kind: Enhancement

Comments

@jacobheun
Copy link
Contributor

In order to help SP's diagnose and fix issues with their system it would be helpful to include a doctor command within Boost to run a full diagnostic of subsystems for known issues. This could help alleviate issues that SP's can remedy manually.

Systems to check (and include commands/docs to run to fix)

⚠️ This list is not exhaustive, we should aggregate other known system checks to include

  • The number of sealed and unsealed sectors should match. Retrievals will fail if there is no unsealed sector.
  • All shards for the dag store should be initialized. Missing shards can result in retrieval failures.
  • ...

Nice to have

  • On Boost restart, surface the latest doctor diagnostic check in the UI.
  • On Boost restart, run and log doctor results so SP's know of immediate issues they should resolve
@LexLuthr
Copy link
Collaborator

LexLuthr commented Jun 9, 2022

  1. mh lookup failed error
  2. Can we surface piece store overview - keys and state (like yes I can fetch data for it)
  3. If a shard cannot initialize - error why?
  4. If there is anything in piece store that does not have corresponding shard

@brendalee
Copy link
Collaborator

@dirkmc is this the current work you're doing, or is the current boost doctor work just a portion of this?

@dirkmc
Copy link
Contributor

dirkmc commented Jan 18, 2023

I think we can close this one as code complete

@dirkmc dirkmc closed this as completed Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ux Area: UX kind/enhancement Kind: Enhancement
Projects
Status: Done
Development

No branches or pull requests

4 participants