Giters

bitshares / bitshares-core

BitShares Blockchain node and command-line wallet

Home Page:https://bitshares.github.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ES `413 Request too large` error with `testnet-6.1.0`

abitmore opened this issue · comments

commented

Bug Description

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)
  • Other (please add below) : ElasticSearch History plugin

Steps To Reproduce
Steps to reproduce the behavior (example outlined below):

  1. Execute API call '...'
  2. Using JSON payload '...'
  3. Received response '...'
  4. 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.

CORE TEAM TASK LIST

  • Evaluate / Prioritize Bug Report
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation
commented

Fixed by #2683.