A Testnet node running the test-6.1.0 tag is unable to sync if
the elasticsearch plugin is enabled, and
both the elasticsearch-operation-object and the elasticsearch-operation-string startup options are true, and
even elasticsearch-bulk-replay is set to 200 (whose default value is 10000), and
all other options are default.
Error messages:
handle_bulk_response ] 413 error: Request too large. Can be low disk space. elasticsearch.cpp:56
It is caused by transfers with huge memos. The size of each transfer is around 400 KB in the serialized form, and the size of the corresponding request to ES is around 1.5 MB in 2 lines. With elasticsearch-bulk-replay = 200, the total request size is around 150 MB. But unfortunately the default maximum request size allowed by ES is 100 MB, so we got the error.
The node is able to sync if elasticsearch-bulk-replay is changed to 100.
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)
[x] Other (please add below) : ElasticSearch History plugin
Steps To Reproduce
Steps to reproduce the behavior (example outlined below):
Execute API call '...'
Using JSON payload '...'
Received response '...'
See error in screenshot
Expected Behavior
A clear and concise description of what you expected to happen.
Screenshots (optional)
If applicable, add screenshots to help explain process flow and behavior.
Host Environment
Please provide details about the host environment. Much of this information can be found running: witness_node --version.
Host OS: [e.g. Ubuntu 18.04 LTS]
Host Physical RAM [e.g. 4GB]
BitShares Version: [e.g. 2.0.180425]
OpenSSL Version: [e.g. 1.1.0g]
Boost Version: [e.g. 1.65.1]
Additional Context (optional)
Add any other context about the problem here.
abitmore
commented
1 year ago
Bug Description
A Testnet node running the
test-6.1.0tag is unable to sync ifelasticsearchplugin is enabled, andelasticsearch-operation-objectand theelasticsearch-operation-stringstartup options aretrue, andelasticsearch-bulk-replayis set to200(whose default value is10000), andError messages:
It is caused by transfers with huge memos. The size of each transfer is around
400 KBin the serialized form, and the size of the corresponding request to ES is around1.5 MBin 2 lines. Withelasticsearch-bulk-replay = 200, the total request size is around150 MB. But unfortunately the default maximum request size allowed by ES is100 MB, so we got the error.The node is able to sync if
elasticsearch-bulk-replayis changed to100.Impacts Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.
Steps To Reproduce Steps to reproduce the behavior (example outlined below):
Expected Behavior A clear and concise description of what you expected to happen.
Screenshots (optional) If applicable, add screenshots to help explain process flow and behavior.
Host Environment Please provide details about the host environment. Much of this information can be found running:
witness_node --version.Additional Context (optional) Add any other context about the problem here.
CORE TEAM TASK LIST