You are viewing a single comment's thread from:

RE: SBDS to MySQL in Docker

in #utopian-io7 years ago

Are your tests still staying current with the head_block_number? My new test that was at 169G about 18 hours ago stopped growing at 177G and I can't get it to pick back up again. Also, my other droplet that was typically within 20 blocks of the current block is now 10,000+ blocks behind. Are you experiencing similar issues?

Sort:  

Generally, I stay within about 20 blocks, but sometimes I'll see exactly what you're describing.

I just stop SBDS, restart, and watch the logs:

# docker stop steem_sbds
# docker start steem_sbds
# docker logs --tail=2 -f steem_sbds
[4/6]   Finding blocks missing from db...
Finding missing block_nums

It'll sit on 'finding' for quite awhile, but soon enough you'll see it writing new blocks.

I'm trying to write a monitoring script that can be called by cron to do all of this automatically.

A monitoring script sounds like a great idea. I'd be happy to help test it out. Various issue's I've experienced are where block height stops going up or one or both of steem_mysql or steem_sbds stops.

That's exactly what I'm seeing, and every time I fix it, the solution is something that could have been scripted. I'll definitely ping you when I have something together for testing.