Update logging and docu

details:
 Reduce some logging noise
 Clarify activating/suspending syncer in log messages

nimbus/sync/beacon/README.md

@@ -66,17 +66,21 @@ Implementation, The Gory Details
 The following diagram depicts a most general state view of the sync and the
 *FC* modules and at a given point of time
 
-        0                    L                                               (5)
-        o--------------------o
+        0         B          L                                               (5)
+        o---------o----------o
         | <--- imported ---> |
                      C                     D                H
                      o---------------------o----------------o
                      | <-- unprocessed --> | <-- linked --> |
 
 where
 
+* *B* -- **base**, current value of this entity (with the same name) of the
+         **FC** module (i.e. the current value when looked up.)
+
 * *C* -- coupler, parent of the left endpoint of the chain of headers or blocks
-         to be fetched and imported.
+         to be fetched and imported. The block number of *C* is somewhere
+		 between the ones of *B* and *C* inclusive.
 
 * *L* -- **latest**, current value of this entity (with the same name) of the
          **FC** module (i.e. the current value when looked up.) *L* need not

nimbus/sync/beacon/worker/db.nim

@@ -114,9 +114,9 @@ proc dbLoadSyncStateLayout*(ctx: BeaconCtxRef; info: static[string]): bool =
     # Add interval of unprocessed header range `(C,D)` from `README.md`
     ctx.headersUnprocSet(ctx.layout.coupler+1, ctx.layout.dangling-1)
 
-    trace info & ": restored sync state", L=latest.bnStr,
+    trace info & ": restored syncer state", L=latest.bnStr,
       C=ctx.layout.coupler.bnStr, D=ctx.layout.dangling.bnStr,
-      F=ctx.layout.final.bnStr, H=ctx.layout.head.bnStr
+      H=ctx.layout.head.bnStr
 
     true
 

nimbus/sync/beacon/worker/start_stop.nim

@@ -122,8 +122,6 @@ proc setupDatabase*(ctx: BeaconCtxRef; info: static[string]) =
   # system becomes fully active. Otherwise there is some polling only waiting
   # for a new target so there is reduced service (aka `hibernate`.).
   ctx.hibernate = not ctx.dbLoadSyncStateLayout info
-  if ctx.hibernate:
-    trace info & ": hibernating", latest=ctx.chain.latestNumber.bnStr
 
   # Set blocks batch import value for block import
   if ctx.pool.nBodiesBatch < nFetchBodiesRequest:

nimbus/sync/beacon/worker/update.nim

@@ -121,8 +121,7 @@ proc startHibernating(ctx: BeaconCtxRef; info: static[string]) =
 
   ctx.hibernate = true
 
-  trace info & ": hibernating, awaiting sync target",
-    L=ctx.chain.latestNumber.bnStr
+  trace info & ": suspending syncer", L=ctx.chain.latestNumber.bnStr
 
   # Update, so it can be followed nicely
   ctx.updateMetrics()
@@ -327,7 +326,7 @@ proc updateFinalBlockHeader*(
     b = ctx.chain.baseNumber()
     f = finHdr.number
   if f < b:
-    trace info & ": finalised number too low",
+    trace info & ": finalised block # too low",
       B=b.bnStr, finalised=f.bnStr, delta=(b - f)
 
     ctx.target.reset
@@ -339,7 +338,7 @@ proc updateFinalBlockHeader*(
     # Activate running (unless done yet)
     if ctx.hibernate:
       ctx.hibernate = false
-      trace info & ": activated syncer",
+      trace info & ": activating syncer", B=b.bnStr,
         finalised=f.bnStr, head=ctx.target.consHead.bnStr
 
     # Update, so it can be followed nicely