Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

R4R: limit range get log #101

Merged
merged 1 commit into from
Mar 9, 2021
Merged

R4R: limit range get log #101

merged 1 commit into from
Mar 9, 2021

Conversation

unclezoro
Copy link
Collaborator

@unclezoro unclezoro commented Mar 4, 2021

Description

GetLog API with unlimited block range will consume huge CPU and IO resource, which has import great pressure to our data seed nodes. As a result, our data seed node always can't sync recent blocks.

Rationale

Add --rangelimit flag to our geth. If a node started with this flag, a default block range limit will be applied to GetLog API, thus the pressure to BSC node will be reduced.

Example

add an example CLI or API response...

Changes

Notable changes:

  • add each change in a bullet point here
  • ...

Preflight checks

  • build passed (make build)
  • tests passed (make test)
  • manual transaction test passed

Already reviewed by

...

Related issues

... reference related issue #'s here ...

@HaoyangLiu HaoyangLiu changed the title [WIP]limit range get log R4R: limit range get log Mar 9, 2021
@yutianwu yutianwu merged commit f16d8e0 into master Mar 9, 2021
@unclezoro unclezoro mentioned this pull request Mar 23, 2021
3 tasks
@unclezoro unclezoro deleted the range branch March 23, 2021 07:18
@saurik
Copy link

saurik commented Apr 2, 2021

(edit: I have moved this comment to #113, which I found someone else had already filed when I decided there should be a top-level issue about this and not just a complaint on an old, already-merged PR.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants