Open NachoDeLaVega opened 2 years ago
GoQuorum 21.1.0 utiliza la versión 1.9.7 de Geth. Según esta guía de Consensys (https://consensys.net/docs/goquorum/en/21.10.0/deploy/upgrade/migration/) ocurre lo siguiente con los datos antiguos (ancient):
freezerdb - geth
1.9.7 introduces the feature of freezerdb where block data beyond a certain threshold is moved to a different file-based storage area. The location for freezerdb can be provided by the geth
command line option:
--datadir.ancient <value>
- Data directory for ancient chain segments (default = inside chaindata
)
When a node is migrated to this version, geth
by default will create the ancient
data folder and start moving blocks below the immutability threshold (default: 3162240) into the ancient data.
If you do not want this movement to happen, use --immutabilitythreshold
to set the immutability threshold to an appropriate value when starting geth
.
He modificado los scripts de arranque de geth para añadir esos parametros:
--datadir.ancient /root/alastria/data/geth/chaindata/ancient/ --immutabilitythreshold 1
Pero el proceso no levanta, mostrando un error en el log
VAL_Alisys_Telsius_2_8_01 | INFO [00-00|00:00:00.000|entrypoint.sh:54] ... nodes recibed
VAL_Alisys_Telsius_2_8_01 | INFO [00-00|00:00:00.000|entrypoint.sh:56] Parsing correct databases
VAL_Alisys_Telsius_2_8_01 | Fatal: Error starting protocol stack: ancient chain segments already extracted, please set --datadir.ancient to the correct path
VAL_Alisys_Telsius_2_8_01 | Fatal: Error starting protocol stack: ancient chain segments already extracted, please set --datadir.ancient to the correct path
Sin embargo, se crea el directorio /root/alastria/data/geth/chaindata/ancient/ con ficheros
ll /root/alastria/data/geth/chaindata/ancient/
total 20
-rw-r--r-- 1 root root 0 jul 5 12:07 bodies.0000.cdat
-rw-r--r-- 1 root root 6 jul 5 12:07 bodies.cidx
-rw-r--r-- 1 root root 0 jul 5 12:07 diffs.0000.rdat
-rw-r--r-- 1 root root 6 jul 5 12:07 diffs.ridx
-rw-r--r-- 1 root root 0 jul 5 12:07 FLOCK
-rw-r--r-- 1 root root 0 jul 5 12:07 hashes.0000.rdat
-rw-r--r-- 1 root root 6 jul 5 12:07 hashes.ridx
-rw-r--r-- 1 root root 0 jul 5 12:07 headers.0000.cdat
-rw-r--r-- 1 root root 6 jul 5 12:07 headers.cidx
-rw-r--r-- 1 root root 0 jul 5 12:07 receipts.0000.cdat
-rw-r--r-- 1 root root 6 jul 5 12:07 receipts.cidx
Can we already mark the issue as solved?
Se han realizado los trabajos de actualización de versiones de nuestro nodo validador (VAL_Alisys_Telsius_2_8_01) de acuerdo con https://github.com/alastria/alastria-node-quorum/pull/29 pero hemos tenido que hacer rollback, dejando el nodo ejecutando la versión anterior: