-
Notifications
You must be signed in to change notification settings - Fork 852
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
eth_getFilterChanges not working since 1.4.x and --auto-log-bloom-caching-enabled=true #473
Comments
Its also important to know which are the server requirements after this new flag auto-log-- We have increased our SSD disco on AWS to 5000 IOPS to reduce IOWAIT, and we needed to increase the machine to 8gb mem and 4 cores to allow indexing and receiving blocks, because if not, node stopped receiving blocks. |
I am also facing this with Besu docker 1.4. Do not get any results for |
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
Thanks for the detailed report! We'll be looking at this in more detail over the next few weeks. |
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
If we detect an EOF for the cache file switch over to an uncached query. This is typically seen when filling a log filter and the new block has not yet written out the log bloom cache to disk. Fixed hyperledger#473 Signed-off-by: Danno Ferrin <[email protected]>
If we detect an EOF for the cache file switch over to an uncached query. This is typically seen when filling a log filter and the new block has not yet written out the log bloom cache to disk. Fixed #473 Signed-off-by: Danno Ferrin <[email protected]>
This should be released in 1.4.3, near the end of next week (8-9 April or thereabouts). Or you can try the dev releases (hyperledger/besu:1.4.3-SNAPSHOT) in the interim to validate. |
Thanks!
El El dom, 29 mar 2020 a las 23:38, Danno Ferrin <[email protected]>
escribió:
This should be released in 1.4.3, near the end of next week (8-9 April or
thereabouts). Or you can try the dev releases
(hyperledger/besu:1.4.3-SNAPSHOT) in the interim to validate.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#473 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKXFDVJ7FXWRBHSTVCCZJTRJ65UXANCNFSM4LL5ZFQA>
.
--
[image: logo] <https://io.builders/>
*io.builders <http://io.builders/>*
Blockchain venture builder *Fernando París*
CTO • ioBUILDERS
Mobile: +34 679 467 927
Parque Científico y Tecnológico UPM Campus de Montegancedo, s/n.
28223 Pozuelo de Alarcón, MADRID
NOTA LEGAL: Este mensaje y cualquier archivo adjunto está destinado
únicamente a quien se dirige y es confidencial. Si usted ha recibido este
mensaje por error, comuníqueselo al remitente y bórrelo inmediatamente. La
utilización, revelación y/o reproducción del mensaje puede constituir un
delito.
PROTECCIÓN DE DATOS – Responsable: ioBUILDERS, S.L., Finalidad. Envío de
información, respuesta a consultas y contactos genéricos, mientras dure
nuestra relación y tengamos su consentimiento. Destinatarios. No se cederán
datos a terceros salvo obligación legal. Derechos. Puede ejercer los
derechos de acceso, rectificación, supresión y oposición, limitar el
tratamiento de sus datos, o directamente oponerse al tratamiento, o ejercer
el derecho a la portabilidad de los mismos. Todo ello, mediante escrito,
acompañado de copia de documento oficial que le identifique, dirigido a
Parque Científico y Tecnológico UPM Campus de Montegancedo, s/n. 28223
Pozuelo de Alarcón, MADRID (España). En caso de disconformidad con el
tratamiento, también tiene derecho a presentar una reclamación ante la
Agencia Española de Protección de Datos. También podrá oponerse a nuestros
envíos de comunicaciones comerciales (Art.21.2 de la LSSI) a través de la
siguiente dirección de correo electrónico: [email protected]
|
Works like a charm! One suggestion. Due that node sometimes, stops receiving blocks until all chain is indexed, i think its worth to add this advice to documentation. kind regards |
Another suggestion came through, due the the time spent caching the whole history and raising high iowait peaks, close to 50%. We suggest to add a cpu, and iowait recommendation in case of cache activation, and highlight full chain cache performance We are almost sure, that this performance bottleneck is the root cuase of nor receiving blocks and focus only on caching. 2020-04-10 09:22:08.706+00:00 | EthScheduler-Timer-0 | INFO | TransactionLogBloomCacher | Caching segment at 4300000 kind regards |
- Update Besu to version 1.4.3 where event bug(hyperledger/besu#473) is fixed - Minor document fix Signed-off-by: Rajeev Ranjan <[email protected]>
- Update Besu to version 1.4.3 where event bug(hyperledger/besu#473) is fixed - Minor document fix Signed-off-by: Rajeev Ranjan <[email protected]>
Awesome!!. Thanks for fixing it so quick. |
- Update Besu to version 1.4.3 where event bug(hyperledger/besu#473) is fixed - Minor document fix Signed-off-by: Rajeev Ranjan <[email protected]>
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
- Downgrade Besu version to 1.3.9. There appears to be some defect in Besu 1.4 onwards around eth_getFilterChanges - hyperledger/besu#473. Reverting to dot release 1.3.9 does not show the issue. - Remove JRPC event handling - Minor bug fix in event formatting - Remove redundant library eth-abi from Dockerfile Signed-off-by: Rajeev Ranjan <[email protected]>
Description
As an Besu user, i want to be able to get filter changes even if loog bloo filters are activated from cli
Acceptance Criteria
Steps to Reproduce (Bug)
Versions (Add all that apply)
Additional Information
On Pegasys jira we opened the root base for the bloom filter inception at PAN-3245. Now this is not working.
Reviewing open issues we thought 1.4.1 fixed issue #438, could help but is not working.
Maybe this is related to this issue and we need to give it try. Please let us know
https://jira.hyperledger.org/projects/BESU/issues/BESU-169?filter=allopenissues
Impact
Any company using consensys/eventeum will not be able to get events. iobuilders has falled back to 1.3.9.
Kind regards
@abdelhamidbakhta
@shemnon
The text was updated successfully, but these errors were encountered: