Consider tuning ancestor/descendant size limit for our use case #139

New issue

Closed

opened 2018-05-16 19:56:28 +02:00 by shyba · 3 comments

shyba commented

2018-05-16 19:56:28 +02:00

(Migrated from github.com)

While publishing lots of videos, @nikooo777 got:
Transaction rejected: 64: too-long-mempool-chain

Which comes from: 4ff143387e/src/main.cpp (L1249)

Which is affected by:
-limitancestorcount
-limitancestorsize
-limitdescendantcount
-limitdescendantsize

At the time it last happened, this was the mempool info output:

[lbry@lbryum8:~] $ ./lbrycrd/lbrycrd-cli getmempoolinfo
{
 "size": 82,
 "bytes": 84031,
 "usage": 159920,
 "maxmempool": 300000000,
 "mempoolminfee": 0.00000000
}

This issue opens a discussion on what would be the best move on this subject and if there are other solutions.

While publishing lots of videos, @nikooo777 got: Transaction rejected: 64: too-long-mempool-chain Which comes from: https://github.com/lbryio/lbrycrd/blob/4ff143387ef98ffb7e57b3b07f11714589f6d85c/src/main.cpp#L1249 Which is affected by: -limitancestorcount -limitancestorsize -limitdescendantcount -limitdescendantsize At the time it last happened, this was the mempool info output: ```bash [lbry@lbryum8:~] $ ./lbrycrd/lbrycrd-cli getmempoolinfo { "size": 82, "bytes": 84031, "usage": 159920, "maxmempool": 300000000, "mempoolminfee": 0.00000000 } ``` This issue opens a discussion on what would be the best move on this subject and if there are other solutions.

👍 1

shyba commented

2018-05-16 20:04:51 +02:00

(Migrated from github.com)

Solution I would consider: What if the node being used for large scale publishes raises this limit? Will the mempool get rejected by other nodes all the time? Would it solve or trigger another issue?

alyssaoc commented

2018-10-17 19:51:46 +02:00

(Migrated from github.com)

@shyba and @nikooo777 Is this still an issue? What is the impact/priority?

alyssaoc commented

2018-12-05 21:02:21 +01:00

(Migrated from github.com)

closing per conversation with Niko and Victor

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#139

No description provided.

Rows
Columns