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

pkg/agent/core/ngt/service/New blocks startup process of agent-ngt #503

Closed
rinx opened this issue Jun 23, 2020 · 3 comments
Closed

pkg/agent/core/ngt/service/New blocks startup process of agent-ngt #503

rinx opened this issue Jun 23, 2020 · 3 comments
Labels

Comments

@rinx
Copy link
Contributor

rinx commented Jun 23, 2020

Describe the bug:

with invalid NGT backup files, pkg/agent/core/ngt/service/New blocks startup process of agent-ngt.

To Reproduce:

put invalid backup files in index_path and enable_in_memory_mode=false.

Expected behavior:

Maybe there are two options to fallback the application. 🤔

  • restart pod and retry to load
  • start daemon without backup data.

Environment:

  • Go Version: 1.14.3
  • Docker Version: 19.03.8
  • Kubernetes Version: 1.18.2
  • NGT Version: 1.11.5
@rinx rinx added type/bug Something isn't working team/core Core team priority/medium labels Jun 23, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label type/bug to this issue, with a confidence of 0.86. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@kpango
Copy link
Collaborator

kpango commented Jun 23, 2020

Thank you for your feedback.
I think restart pod and download again looks good.
If we start daemon without backup data, S3 back up data will be overwritten, it makes problem for data consistency

@rinx
Copy link
Contributor Author

rinx commented Jul 22, 2020

resolved in #503

@rinx rinx closed this as completed Jul 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants