You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nodes table contain entries for both current online nodes and those that were online in the past. Over time the nodes table will grow indefinitely. A process should be put in place to prune old nodes -- say over 24 hours --- to prevent the table from getting too large.
The text was updated successfully, but these errors were encountered:
Yea, node IDs are generated on every startup of the Tork process and never reused. After 5 minutes a node is considered offline. 24 hours seems quite safe. If for some random reason a worker sends a hearbeat more than 24 hours later it will simply create the record again in the DB.
That being said, the TTL should probably be configurable in case certain administrators want to retain them longer for analysis purposes or some such thing.
The
nodes
table contain entries for both current online nodes and those that were online in the past. Over time the nodes table will grow indefinitely. A process should be put in place to prune old nodes -- say over 24 hours --- to prevent the table from getting too large.The text was updated successfully, but these errors were encountered: