Online Nodes not reporting correct numbers

lukeskinner commented 4 years ago

Online nodes was showing 0 nodes due to an issue with the job scheduler.

Action items:

[x] Restart services
[x] Check mainnet node is responding and running latest version
[x] Write a query to find nodes winning jobs but are 'offline' according to OT Hub
[x] Test API calls to the mainnet node using nodes found that are 'offline' in above query

lukeskinner commented 4 years ago

Rebooting the service has helped but I have a hunch it's not pulling new nodes into the calculation.

lukeskinner commented 4 years ago

This is now fixed. Around 350 nodes were picked up in addition to what it previously had.

Changes made:

[x] Fixed json response definition not matching between OT Hub and the OT node
[x] Adjusted SQL for pulling back nodes to query against the OT node to be smarter so it now looks at previous online checks. If a node hasn't been seen online in the last 24 hours it will query the OT node to see if it has a newer ip/port.
[x] When a node is found for the first time or updated it will insert a history record so that the node will report as 'online' if people view it on ot hub. History records were previously only inserted on the scheduled hourly uptime check.

OT-Hub / OTHub