You are viewing a single comment's thread from:

RE: Setup a Hive witness using the new rolling block log feature

in #witness • 8 months ago (edited)

Full set of .artifacts is 2GB, not 100 :o)

Depends on how long it has been running for. Mine is 97G and slowly growing. I believe mine is experiencing a bug, because most of my nodes are ~2GB, but some are growing.

image.png

One of the features of split block log is the ability to share all but last part. You can have multiple nodes that use the same block log parts and related artifacts symlinked to their .blockchain folders from the same actual storage location.

I believe this is what someguy does with his hosted witness node service.

8 months ago in #witness by
$0.00
    15 votes
    Reply 4
    Sort:  
  • Trending
    • [-]
     8 months ago  

    I wonder how does it even work (what is the content of your .artifacts) - valid file contains header (artifact_file_header) and then one 24 byte record for each block (artifact_file_chunk). If your file is bigger it definitely points to a bug. Your log might already contain some info pointing to source of a problem (look for messages originating from block_log_artifacts.cpp or any warnings/errors related to block log).

    $0.05
    • Past Payouts $0.05
    • - Author $0.03
    • - Curators $0.03
    1 vote
    Reply
    [-]
     8 months ago  

    I was going to blow the node away since my other nodes it is 2.2GB or so, but this one it just has been growing, but if I can get some information on where this bug is coming from, it would be helpful to resolve it.