<p>The best step is stopping the node correctly which can vary a bit on how you run the cardano-node</p>
<p>Another thing that I do is dump the ledger before rebooting
So I look at the current block. For example right now 72849870
Also you need to put the path to your ~/cardano-node/db/ledger (for my build for example)</p>
<p>The command then is as follows:
cardano-cli query ledger-state --mainnet --out-file ~/cardano-node/db/ledger/72849870</p>

CC BY-SA 4.0
2022-09-29T04:49:08.030Z
Thanks for the reply! I will try!
Satish
CC BY-SA 4.0
2022-09-29T01:54:08.600Z
2022-09-29T01:54:08.600Z
Jon_IRF
<p>I run not only Cardano nodes but also Ethereum and other nodes.</p>
<p>I think the downtime is longer when upgrading or restarting a Cardano node compared to other nodes.<br />
Downtime here is the time between when a node is restarted and when it starts synchronizing blocks again.<br />
It took over an hour for Mainnet to start synchronizing.<br />
It cannot be any other node.</p>
<p>I have three questions.</p>
<ol>
<li>Why does it take so long for the Cardano node?</li>
<li>Is there any way to reduce the downtime?</li>
<li>Is there anything the community can do to improve downtime?</li>
</ol>
<p>Best Regard!!<br />
Any advice is welcome.</p>
<p>The specifications are as follows</p>
<ul>
<li>Cardano-node
<ul>
<li>CPU: 4</li>
<li>Memory: 16Gi</li>
</ul>
</li>
<li>Ogmios
<ul>
<li>CPU: 500m</li>
<li>Memory: 16Gi</li>
</ul>
</li>
<li>Postgres
<ul>
<li>CPU: 8</li>
<li>Memory: 32Gi</li>
</ul>
</li>
<li>GraphQL
<ul>
<li>CPU: 2</li>
<li>Memory: 4Gi</li>
</ul>
</li>
<li>DBSync
<ul>
<li>CPU: 4</li>
<li>Memory: 32Gi</li>
</ul>
</li>
<li>Hasura
<ul>
<li>CPU: 500m</li>
<li>Memory: 2Gi</li>
</ul>
</li>
</ul>

CC BY-SA 4.0
2022-09-28T03:35:40.017Z
How are you stopping the `node`? If the `node` is sent a `SIGTERM` the `node` will do a safe shutdown (I have seen this take up to 5 minutes) which results in a quicker restart (under 10 minutes in my experience). If the `node` does not shut down safely (or the safe shutdown did not complete) then startup will be longer. Also be aware that when there is a change in the on-disk storage format, a complete rebuild will be necessary.
Erik de Castro Lopo
CC BY-SA 4.0
2022-09-29T00:18:48.363Z
Thanks for the reply!  
I'm using ArgoCD to manage my nodes, but I don't shut them down and let them reboot or adapt to version changes without shutting them down.  
How do I do a safe shutdown?
Best Regard!! Thank you.
Satish
CC BY-SA 4.0
2022-09-29T02:48:58.697Z
Sorry, no idea. you should ask the people who develop ArgoCD.
Erik de Castro Lopo
<cardano-node><cardano-db-sync><syncing>
Downtime when upgrading or restarting a node
# Downtime when upgrading or restarting a node

(Asked by: username_0 on 2022-09-28)

I run not only Cardano nodes but also Ethereum and other nodes.

I think the downtime is longer when upgrading or restarting a Cardano node compared to other nodes.  
Downtime here is the time between when a node is restarted and when it starts synchronizing blocks again.  
It took over an hour for Mainnet to start synchronizing.  
It cannot be any other node.

I have three questions.

1. Why does it take so long for the Cardano node?
2. Is there any way to reduce the downtime?
3. Is there anything the community can do to improve downtime?

Best Regard!!  
Any advice is welcome.

The specifications are as follows

* Cardano-node
  + CPU: 4
  + Memory: 16Gi
* Ogmios
  + CPU: 500m
  + Memory: 16Gi
* Postgres
  + CPU: 8
  + Memory: 32Gi
* GraphQL
  + CPU: 2
  + Memory: 4Gi
* DBSync
  + CPU: 4
  + Memory: 32Gi
* Hasura
  + CPU: 500m
  + Memory: 2Gi

**Tags:** cardano-node, cardano-db-sync, syncing
> **Comments:**
> **username_1**: How are you stopping the `node`? If the `node` is sent a `SIGTERM` the `node` will do a safe shutdown (I have seen this take up to 5 minutes) which results in a quicker restart (under 10 minutes in my experience). If the `node` does not shut down safely (or the safe shutdown did not complete) then startup will be longer. Also be aware that when there is a change in the on-disk storage format, a complete rebuild will be necessary.  
> **username_0**: Thanks for the reply!   I'm using ArgoCD to manage my nodes, but I don't shut them down and let them reboot or adapt to version changes without shutting them down.   How do I do a safe shutdown? Best Regard!! Thank you.  
> **username_1**: Sorry, no idea. you should ask the people who develop ArgoCD.  

---

## 1 answers

### Answer by username_2 on 2022-09-29. Score: 0 | Accepted answer

The best step is stopping the node correctly which can vary a bit on how you run the cardano-node

Another thing that I do is dump the ledger before rebooting
So I look at the current block. For example right now 72849870
Also you need to put the path to your ~/cardano-node/db/ledger (for my build for example)

The command then is as follows:
cardano-cli query ledger-state --mainnet --out-file ~/cardano-node/db/ledger/72849870

> **Comments:**
> **username_0**: Thanks for the reply! I will try!  

---

