mirror of
https://github.com/hoytech/strfry.git
synced 2025-06-17 16:58:50 +00:00
remove relay__negentropy__maxFilterLimit for now
- this was causing problems on big DBs - need more reliable way of enforcing limits
This commit is contained in:
2
golpe
2
golpe
Submodule golpe updated: 6d0c7897b4...79ae8de092
@ -121,7 +121,7 @@ void RelayServer::ingesterProcessNegentropy(lmdb::txn &txn, Decompressor &decomp
|
|||||||
if (arr.get_array().size() < 5) throw herr("negentropy query missing elements");
|
if (arr.get_array().size() < 5) throw herr("negentropy query missing elements");
|
||||||
|
|
||||||
NostrFilterGroup filter;
|
NostrFilterGroup filter;
|
||||||
auto maxFilterLimit = cfg().relay__negentropy__maxFilterLimit;
|
auto maxFilterLimit = MAX_U64;
|
||||||
|
|
||||||
if (arr.at(2).is_string()) {
|
if (arr.at(2).is_string()) {
|
||||||
auto ev = lookupEventById(txn, from_hex(arr.at(2).get_string()));
|
auto ev = lookupEventById(txn, from_hex(arr.at(2).get_string()));
|
||||||
|
@ -94,7 +94,3 @@ config:
|
|||||||
desc: negentropy threads: Handle negentropy protocol messages
|
desc: negentropy threads: Handle negentropy protocol messages
|
||||||
default: 2
|
default: 2
|
||||||
noReload: true
|
noReload: true
|
||||||
|
|
||||||
- name: relay__negentropy__maxFilterLimit
|
|
||||||
desc: "Maximum records that can be processed per filter"
|
|
||||||
default: 1000000
|
|
||||||
|
@ -124,9 +124,4 @@ relay {
|
|||||||
# negentropy threads: Handle negentropy protocol messages (restart required)
|
# negentropy threads: Handle negentropy protocol messages (restart required)
|
||||||
negentropy = 2
|
negentropy = 2
|
||||||
}
|
}
|
||||||
|
|
||||||
negentropy {
|
|
||||||
# Maximum records that can be processed per filter
|
|
||||||
maxFilterLimit = 1000000
|
|
||||||
}
|
|
||||||
}
|
}
|
||||||
|
Reference in New Issue
Block a user