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

Error populating ES database, we are going to keep trying. #1953

Closed
17 tasks
abitmore opened this issue Aug 22, 2019 · 3 comments · Fixed by #2245
Closed
17 tasks

Error populating ES database, we are going to keep trying. #1953

abitmore opened this issue Aug 22, 2019 · 3 comments · Fixed by #2245

Comments

@abitmore
Copy link
Member

Bug Description

Got Error populating ES database, we are going to keep trying. when replaying. Don't know what's wrong.

I think the plugin should at least print the underlying error in console/logs.

database().applied_block.connect([this](const signed_block &b) {
if (!my->update_account_histories(b))
FC_THROW_EXCEPTION(graphene::chain::plugin_exception,
"Error populating ES database, we are going to keep trying.");
});

Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.

  • API (the application programming interface)
  • Build (the build process or something prior to compiled code)
  • CLI (the command line wallet)
  • Deployment (the deployment process after building such as Docker, Travis, etc.)
  • DEX (the Decentralized EXchange, market engine, etc.)
  • P2P (the peer-to-peer network for transaction/block propagation)
  • Performance (system or user efficiency, etc.)
  • Protocol (the blockchain logic, consensus, validation, etc.)
  • Security (the security of system or user data, etc.)
  • UX (the User Experience)
  • Other (please add below)

CORE TEAM TASK LIST

  • Evaluate / Prioritize Bug Report
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation
@abitmore abitmore added this to the 4.1.0 - Feature Release milestone Aug 22, 2019
@oxarbitrage
Copy link
Member

Ill see what i can do.

FYI: the most probable reasons are elasticsearch endpoint down or disk full.

@abitmore
Copy link
Member Author

Done some work in #2189. More work in #2245.

@abitmore
Copy link
Member Author

Fixed by #2189 and #2245.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants