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

Provide easy/clear notification/error if falling behind reproviding #9702

Closed
BigLep opened this issue Mar 8, 2023 · 0 comments · Fixed by #9886
Closed

Provide easy/clear notification/error if falling behind reproviding #9702

BigLep opened this issue Mar 8, 2023 · 0 comments · Fixed by #9886
Assignees

Comments

@BigLep
Copy link
Contributor

BigLep commented Mar 8, 2023

Done Criteria

There is a clear error message in logs AND metric for when we fail to provide within the configured interval.

Why Important

This makes it more self-service for content providers to understand why their content may not be discoverable by others. Kubo maintainers have seen various cases of content not being discoverable because a provider was unknowingly not refreshing the DHT before record expiration.

User/Customer

Mostly like operators with large pinsets.

Notes

Ideally any error message, should have suggestions of what can do. For example, if they don’t have the accelerated DHT enabled, that should be considered.

We want log messages and a metric to increase the the likelihood for an operator to detect this failure mode.

@BigLep BigLep moved this to 🥞 Todo in IPFS Shipyard Team Mar 8, 2023
@BigLep BigLep mentioned this issue Apr 4, 2023
@Jorropo Jorropo moved this from 🥞 Todo to 🏃‍♀️ In Progress in IPFS Shipyard Team May 11, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue May 15, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue May 15, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue May 19, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue May 19, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue May 22, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue May 31, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 1, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 2, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 2, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 2, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 2, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 2, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 2, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 7, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 7, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 7, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 7, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 8, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 8, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 8, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 8, 2023
Jorropo added a commit to Jorropo/go-ipfs that referenced this issue Jun 8, 2023
Jorropo added a commit that referenced this issue Jun 8, 2023
@github-project-automation github-project-automation bot moved this from 🏃‍♀️ In Progress to 🎉 Done in IPFS Shipyard Team Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants