nimbus-eth1

History

Jordan Hrycaj f40a066cc6 Update snap sync ready to succeed at lab test (#1556 ) * Extract RocksDB timing tests from snap unit tests as separate module why: Declutter, make space for more snap related unit tests. * Renamed `undumpNextGroup()` => `undumpBlocks()` why: Source file name is called `undump_blocks.nim` which should be sort of in sync with the method name(s). * Implement snap/1 server method `getByteCodes()` * Implement snap/1 client method `getByteCodes()` * Implement faculty for handling contract code fetching via snap/1 * Provide persistent storage for contract code records * Implement contract code snap sync fetch & store * Code massage, cosmetics * Unit tests for verifying snap sync snapshot dump details: Use `undump_kvp.dumpAllDb()` to dump any database.		2023-04-21 22:11:04 +01:00
..
worker	Update snap sync ready to succeed at lab test (#1556 )	2023-04-21 22:11:04 +01:00
README.txt	Prepare snap server client test scenario cont4 (#1507 )	2023-03-17 14:46:50 +00:00
constants.nim	Update snap sync ready to succeed at lab test (#1556 )	2023-04-21 22:11:04 +01:00
range_desc.nim	Update snap sync ready to succeed at lab test (#1556 )	2023-04-21 22:11:04 +01:00
update_beacon_header.nim	Prepare snap client for continuing with full sync (#1534 )	2023-04-06 20:42:07 +01:00
worker.nim	Pre functional snap to full sync (#1546 )	2023-04-14 23:28:57 +01:00
worker_desc.nim	Update snap sync ready to succeed at lab test (#1556 )	2023-04-21 22:11:04 +01:00

README.txt

Snap sync test & debugging scenario
===================================


Start snap/1 server
-------------------

  # Enter nimbus directory for snap/1 protocol server.
  cd server

  # Tell nimbus to stop full sync after 2 mio blocks.
  echo 2000000 > full-limit.txt

  # Tell nimbus to use this predefined key ID
  echo 123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0 > full-id.key

  ./build/nimbus \
    --tcp-port:30319 --nat=None --sync-mode=full \
	--protocols=snap --discovery=none \
	--net-key=./full-id.key \
	--sync-ctrl-file=./full-limit.txt \
	--log-level:TRACE

  # Wait for several hours until enough blocks have been downloaded so that
  # snap sync data are available. The full 2 mio blocks are available if the
  # log ticker shows something like
  #
  # INF 2023-03-17 [..] Sync statistics (suspended) topics="full-tick" [..] persistent=#2000080 [..]
  #
  # where the persistent=#2000080 field might vary


Start snap/1 client
-------------------

  # Note: When the snap/1 server has enough blocks, the client can be started.

  # Enter nimbus directory for snap/1 protocol server
  cd client

  # Tell nimbus to use this pivot block number. This number must be smaller
  # than the 2000000 written into the file full-limit.txt above.
  echo 600000 > snap/snap-update.txt.

  # Tell nimbus to use this hard coded peer enode.
  echo enode://192d7e7a302bd4ff27f48d7852621e0d3cb863a6dd67dd44e0314a25a3aa866837f0d2460b4444dc66e7b7a2cd56a2de1c31b2a2ba4e23549bf3ba3b0c4f2eb5@127.0.0.1:30319 > snap/full-servers.txt

  ./build/nimbus \
    --tcp-port:30102 --nat=None --sync-mode=snap \
	--protocols=none --discovery=none \
	--static-peers-file=./full-servers.txt \
	--sync-ctrl-file=./snap-update.txt \
	--log-level:TRACE


Modifications while the programs are syncing
--------------------------------------------

  # Increasing the number in the files full/full-limit.txt or
  # snap/snap-update.txt will be recognised while running. Decreasing
  # or removing will be ignored.