Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Tom Bradshaw
  • crown-corecrown-core
  • Issues
  • #10

Closed
Open
Created Jan 21, 2019 by Mark Brooker@walkjivefly

Lumpy chain

Summary

Block generation is anything but smooth and the chain is "lumpy"

Steps to reproduce

Just observe the block production times in testnet

Expected behavior

A new block should be generated about every 1 minute

Problematic behavior

The generation interval varies between a few seconds up to tens of minutes (longest observed so far 66 minutes)

Crown-core environment info

Ubuntu 16.04.

Crown-core application info

Crown version v0.12.7.1-2029222a pipeline 873

Relevant logs and/or screenshots

Today the chain froze after block 19841 for an hour. Seen from my wallet the frozen period was

2019-01-21 10:55:10 UpdateTip: new best=e48db9168a69d114cf132d254362354f70b49003b4d787db2bedfe051c7b1576  height=19841  log2_work=40.725954  tx=29977  date=2019-01-21 10:54:58 progress=0.999987  cache=0.6MiB(2825tx)
2019-01-21 11:55:10 UpdateTip: new best=69205d93b384df7d1ecb61ff732103be3208033bbaf0692e19a298700307f300  height=19842  log2_work=40.726364  tx=29980  date=2019-01-21 11:55:36 progress=1.000028  cache=0.6MiB(2828tx)

I have attached the debug.log from the MN which (I think was trying and failing to generate the next block for this period. freeze_extract.log

Possible fixes

(Any comments on what you think might be responsible for the problem, if you have particular insight.)

/cc @finjosh

Assignee
Assign to
Time tracking