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
Experiencing 100% disk IO on node running Emerald paratime.
ISSUE TYPE
Bug Report
COMPONENT NAME
emerald paratime
OASIS NODE VERSION
Oasis core 21.3.9
emerald 7.1.0
OS / ENVIRONMENT
STEPS TO REPRODUCE
ACTUAL RESULTS
We are seeing periods of 100% disk I/O utilization on 2 nodes running Emerald paratime.
I/O utilization spikes up on both nodes at the same time.
Both nodes use NVME in RAID0 mode.
The same issue was seen on Emerald ver 6.*
Nodes running Cipher paratime do not exhibit the same behavior.
See screenshots below:
NODE 1:
NODE 2:
Please check if this might be causing transaction processing delays.
The text was updated successfully, but these errors were encountered:
I would guess that extended periods (1-2hours) of 100% IO utilization are Compaction events, which happen every day.
Do you have a network-wide graph of average Emerald block time, so we can correlate if slow block generation can be caused by compaction events happening on multiple node simultaneously? They tend to happen about the same time on both of our Emerald nodes.
Another point: Is pruning enabled by default for Emerald paratime DB?
We see that the duration of 100% I/O utilization period greatly increases with the size of DB.
Currently 76GB Emerald DB takes ~2.5hours to compact.
SUMMARY
Experiencing 100% disk IO on node running Emerald paratime.
ISSUE TYPE
COMPONENT NAME
emerald paratime
OASIS NODE VERSION
Oasis core 21.3.9
emerald 7.1.0
OS / ENVIRONMENT
STEPS TO REPRODUCE
ACTUAL RESULTS
We are seeing periods of 100% disk I/O utilization on 2 nodes running Emerald paratime.
I/O utilization spikes up on both nodes at the same time.
Both nodes use NVME in RAID0 mode.
The same issue was seen on Emerald ver 6.*
Nodes running Cipher paratime do not exhibit the same behavior.
See screenshots below:
NODE 1:
NODE 2:
Please check if this might be causing transaction processing delays.
The text was updated successfully, but these errors were encountered: