* [explorer] added caching fix at flushing db.
* [explorer] fixed all rpc points
* [explorer] small change to refactor storage.Start
* [explorer] fix go test
* [explorer] further increase the batch size
* [explorer] release lock during db writing data
* [explorer] change to rlock/runlock at flushLocked
* [explorer] also add flush time mechanism to trigger flushing
* [explorer] when checking checkpoint, first check memory, then check db
* [p2p] ban beacon node sync message where block height is smaller than current height
* small param change
* small wording fix
* elaborate log message
* fix spelling
During the p2p message validation, the node will drop the node message if
the size is bigger than the MaxPoolTransactionDataSize.
The initial value was just a heuristic value set during the open staking testnet.
However, the valid node message becomes
bigger now due to the higher tx count in the mainnet. So we need to lift the
upper bound. We have observed the oversized node message from metrics.
Ex,
use `curl http://localhost:9900/metrics | grep ^hmy_p2p` to check the metrics
hmy_p2p_node_msg{type="invalid_oversized"} 3484
Signed-off-by: Leo Chen <leo@harmony.one>
* Add rate limit to metrics
* Compliance with harmony's metrics specifications
* Improve rate limit metrics info
* minor: remove the redundancy of rpc metrics name
Signed-off-by: Leo Chen <leo@harmony.one>
* [rpc] set default rate limit to 1000
Signed-off-by: Leo Chen <leo@harmony.one>
* [rpc] fix test errors
Signed-off-by: Leo Chen <leo@harmony.one>
* [metrics] init rpc rate limiter
Signed-off-by: Leo Chen <leo@harmony.one>
Co-authored-by: Leo Chen <leo@harmony.one>
* [cmd] added --sync as the switch of stream sync protocol
* [cmd] minor formatting fix and optimization
* [cmd] add sanity fixes for compatible for last v2.0.0 config files
Leo Chen
Jacky Wang
Rongjian Lan
peekpi
Soph N
Peter Chung
xiaohuo
niklr
MathxH Chen