You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there is something wrong on bulk insertion, the first error could be caused by a block which is many blocks prior to the head block, which means the block is likely not in the undo database. In this case, when shutting down the application, the object database would be at the state of the last irreversible block, but the latest data in the ES database would be before the block which caused the error. It means there would be data missing in the ES database, and the missing data won't be re-added to ES when restarting the application.
Note: this is annoying in development and testing, but less problematic in production.
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
The text was updated successfully, but these errors were encountered:
Bug Description
When there is something wrong on bulk insertion, the first error could be caused by a block which is many blocks prior to the head block, which means the block is likely not in the undo database. In this case, when shutting down the application, the object database would be at the state of the last irreversible block, but the latest data in the ES database would be before the block which caused the error. It means there would be data missing in the ES database, and the missing data won't be re-added to ES when restarting the application.
Note: this is annoying in development and testing, but less problematic in production.
Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.
CORE TEAM TASK LIST
The text was updated successfully, but these errors were encountered: