Author | SHA1 | Message | Date |
---|---|---|---|
Anton Kaliaev |
77deb710fb
|
mempool: disable MaxBatchBytes (#5800)
@p4u from vocdoni.io reported that the mempool might behave incorrectly under a high load. The consequences can range from pauses between blocks to the peers disconnecting from this node. My current theory is that the flowrate lib we're using to control flow (multiplex over a single TCP connection) was not designed w/ large blobs (1MB batch of txs) in mind. I've tried decreasing the Mempool reactor priority, but that did not have any visible effect. What actually worked is adding a time.Sleep into mempool.Reactor#broadcastTxRoutine after an each successful send == manual control flow of sort. As a temporary remedy (until the mempool package is refactored), the max-batch-bytes was disabled. Transactions will be sent one by one without batching Closes #5796 |
4 years ago |
Anton Kaliaev |
6a056e050c
|
mempool: introduce KeepInvalidTxsInCache config option (#5813)
When set to true, an invalid transaction will be kept in the cache (this may help some applications to protect against spam). NOTE: this is a temporary config option. The more correct solution would be to add a TTL to each transaction (i.e. CheckTx may return a TTL in ResponseCheckTx). Closes: #5751 |
4 years ago |
Callum Waters |
ebff8a96a5
|
docs: use hyphens instead of snake case (#5802) | 4 years ago |
Anton Kaliaev |
243ff4b43d
|
blockchain/v1: remove in favor of v2 (#5728) | 4 years ago |
Marko |
69dd8fea9d
|
docs: add nodes section (#5604)
## Description - separate docs related to running nodes into the nodes dir. - keep old files but dont display them - bring over debugging like a pro blog Closes: #XXX |
4 years ago |