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
Hey, I'm running a blockchain node that exposes a blockheight value which increases by 1 every second—or sometimes every 20 seconds. At a certain blockheight, I need to shut down the process, swap the binary, and restart the node for an upgrade.
I'm using curl to keep checking the blockheight until it reaches a specific value. But if the blockheight update is slow, like taking a day, this task could run for several days. My concern is whether Semaphore might have any issues with such long-running tasks, especially regarding SSH connections. Are there any configurations I should adjust to keep the SSH connection stable?
Thanks!
Related to
No response
The text was updated successfully, but these errors were encountered:
Question
Hey, I'm running a blockchain node that exposes a blockheight value which increases by 1 every second—or sometimes every 20 seconds. At a certain blockheight, I need to shut down the process, swap the binary, and restart the node for an upgrade.
I'm using curl to keep checking the blockheight until it reaches a specific value. But if the blockheight update is slow, like taking a day, this task could run for several days. My concern is whether Semaphore might have any issues with such long-running tasks, especially regarding SSH connections. Are there any configurations I should adjust to keep the SSH connection stable?
Thanks!
Related to
No response
The text was updated successfully, but these errors were encountered: