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

Local txs always pending and stayed in the queue #14193

Open
1 task done
swift1911 opened this issue Feb 4, 2025 · 0 comments
Open
1 task done

Local txs always pending and stayed in the queue #14193

swift1911 opened this issue Feb 4, 2025 · 0 comments
Assignees
Labels
A-tx-pool Related to the transaction mempool C-bug An unexpected or incorrect behavior

Comments

@swift1911
Copy link

swift1911 commented Feb 4, 2025

Describe the bug

Some local txs always pending and stayed in the queue, restart can not remove it from the queue and new transaction can not be sent with the error "txpool is full"

Is there any way to setup the lifetime for local txs like geth or delete it from disk?

There is no txpool-transactions-backup.rlp file found in reth-data dir

Here is the response for txpool_status
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"pending": "0x1",
"queued": "0x22"
}
}

start command:

./op-reth node
--datadir="$RETH_DATA_DIR"
--log.stdout.format log-fmt
--enable-discv5-discovery
--ws
--ws.origins=""
--ws.addr=0.0.0.0
--ws.port="$WS_PORT"
--ws.api=eth,net,txpool
--http
--http.corsdomain="
"
--http.addr=0.0.0.0
--http.port="$RPC_PORT"
--http.api=admin,eth,net,txpool
--authrpc.addr=0.0.0.0
--authrpc.port="$AUTHRPC_PORT"
--authrpc.jwtsecret="$OP_NODE_L2_ENGINE_AUTH"
--metrics=0.0.0.0:"$METRICS_PORT"
--chain "$RETH_CHAIN"
--rollup.sequencer-http=$RETH_SEQUENCER_HTTP
--rollup.disable-tx-pool-gossi

Steps to reproduce

  1. send 1000 transactions with 100 concurrency
  2. found out some transactions can not be sent to the base sequencer
  3. restart reth can not get the pending and queued transaction deleted
  4. new transaction can not be sent with "txpool is full"

Node logs

No error logs were found

Platform(s)

Linux (x86)

Container Type

Docker

What version/commit are you on?

1.1.5

What database version are you on?

Current database version: 2
Local database version: 2

Which chain / network are you on?

base

What type of node are you running?

Pruned with custom reth.toml config

What prune config do you use, if any?

[prune]
block_interval = 2

[prune.segments]
sender_recovery = "full"
transaction_lookup = { distance = 10_064 }
account_history = { distance = 10_064 }
storage_history = { distance = 10_064 }
receipts = { distance = 200_0000 }

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

  • I agree to follow the Code of Conduct
@swift1911 swift1911 added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Feb 4, 2025
@mattsse mattsse self-assigned this Feb 4, 2025
@mattsse mattsse added A-tx-pool Related to the transaction mempool and removed S-needs-triage This issue needs to be labelled labels Feb 4, 2025
@mattsse mattsse moved this from Todo to In Progress in Reth Tracker Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-tx-pool Related to the transaction mempool C-bug An unexpected or incorrect behavior
Projects
Status: In Progress
Development

No branches or pull requests

2 participants